dragon-hunt

Runs adversarial end-to-end bug hunts across auth, data, API, and deployment surfaces.

Updated Sep 14, 2026
One-click install
npx skills add https://github.com/Lawrence908/chiron --skill dragon-hunt-lawrence908
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dragon-hunt
Source: https://github.com/Lawrence908/chiron/tree/main/plugins/dev/skills/dragon-hunt
Command: npx skills add https://github.com/Lawrence908/chiron --skill dragon-hunt-lawrence908

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Passing happy-path tests does not mean a system is ready for real users or public exposure. This Skill performs an adversarial audit that finds real bugs, proves them with reproductions, fixes them, and leaves durable evidence before launch. ## Core Features & Use Cases - Seven-Surface Hunt Map: Systematically probes auth and sessions, authorization boundaries, input and upload handling, critical product journeys, API/MCP/agent surfaces, persistence and deployment assumptions, and visual integrity. - Proof Loop: Every suspected bug must be reproduced, covered by a failing test where practical, patched at the owning surface, and re-verified before being logged. - Safety Guardrails: Prohibits destructive probes against live data, requires confirmation before touching shared mounts, and mandates cleanup of started sessions. - Use Case: Before exposing a self-hosted app through a reverse proxy, run a full hunt to catch open redirects, cross-user data access, silent production fallbacks, and broken mobile layouts. ## Quick Start Run an adversarial bug hunt across this app before we expose it publicly, and prove, fix, and log every defect you find.

Frequently Asked Questions about dragon-hunt

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run an adversarial bug hunt before launching an app?▼

Work through the seven hunt surfaces: auth and sessions, authorization boundaries, input handling, critical user journeys, API and MCP surfaces, deployment assumptions, and visual integrity. Reproduce each suspected bug, patch the owning surface, and verify with tests before logging it.

What is the difference between a bug hunt and a code review?▼

A bug hunt ignores diff boundaries and attacks the whole running system like a chaotic user plus a skeptical security reviewer. Code review examines a specific change set; use a dedicated code-review skill for single pull requests instead.

Can I use adversarial testing against a production deployment?▼

Only with strict guardrails: never run destructive probes against live data, snapshot or use fixtures first, avoid writes to production volumes, and confirm before touching network-backed or shared mounts. Stop any servers or sessions you started.

When should I not use an end-to-end bug hunt?▼

Skip it for single pull requests or narrow diffs, purely visual defects, and architecture or modularity concerns. Those cases are better served by code review, visual QA verification, or a full systems audit respectively.

Why do bugs keep recurring after being fixed?▼

Recurring bugs often mean the fix patched a symptom in a caller instead of the surface that owns the bug, or that deployment assumptions differ between local and production environments. Reproduce the failure, fix the owning surface, and add a regression test.