What problem does it solve? Bug bounty hunters often waste sessions wandering without a goal, report hygiene findings that get rejected as N/A, or get stuck in rabbit holes. This Skill provides a master orchestrator that structures every hunting session around a 5-phase non-linear workflow (Recon, Mapping, Discovery, Prove & Escalate, Validate & Report) combined with a critical thinking framework covering developer psychology, anomaly detection, and What-If experiments. ## Core Features & Use Cases - Engagement Mode Confirmation: Distinguishes bug bounty, red team, pentest, and internal audit engagements so only impact-demonstrated findings get reported on bounty platforms. - 5-Phase Non-Linear Workflow: Routes between Recon, Mapping, Vulnerability Discovery, Escalation, and Reporting with explicit decision tables, tool routing (subfinder, nuclei, ffuf, dalfox, interactsh), and 20-minute rotation rules. - False-Positive Prevention Discipline: Enforces marker discipline, body-diff verification, statistical sampling for timing claims, and a shell-loop ban to eliminate retracted findings. - Use Case: Starting a session on a new HackerOne program, invoke this Skill to define a daily goal (e.g., IDOR on the orders API for account takeover), follow the phase checklists, escalate a confirmed IDOR to ATO, and pass the 7-question validation gate before writing the report. ## Quick Start Start a bug bounty hunting session on target example.com and ask what phase to begin with and which vulnerability classes to focus on first.