What problem does it solve? Bug bounty hunters often confirm a valid but low-severity finding (open redirect, DNS-only SSRF, missing rate limit) and leave payout on the table because they don't know which secondary bugs to look for. This Skill maps a confirmed finding to the most likely companion vulnerabilities and known high-value chain patterns. ## Core Features & Use Cases - A→B Signal Table: Given a confirmed bug class (IDOR, SSRF, XSS, SQLi, file upload, OAuth, GraphQL, race condition, S3 exposure, prompt injection), it lists the exact B and C candidates to test next. - Documented Chain Patterns: Includes six worked chains such as S3→JS bundle→OAuth secret, open redirect→OAuth code theft→ATO, XSS→CSRF→admin action, and SSRF→cloud metadata→IAM credentials. - Discipline Rules: Enforces Gate 0 validation for each link, requires separate reports per confirmed bug, and applies 20-minute time-boxing plus rabbit-hole stop signals. - Use Case: You confirmed an open redirect classified as Low. Invoke /chain, describe the finding, and get directed to test OAuth redirect_uri abuse for a full account-takeover chain. ## Quick Start Invoke /chain and describe your confirmed bug including its class, endpoint, current impact, and target platform to get candidate chain paths.