/triage-validation
First NO = KILL. Do not continue.
$ npx -y skills add H-mmer/pentest-agents --skill triage-validation --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/triage-validation
Context preview
The summary Claude sees to decide when to auto-load this skill.
First NO = KILL. Do not continue.
SKILL.md
triage-validation.SKILL.mdTriage & Validation
The 7-Question Gate (applied to EVERY finding)
First NO = KILL. Do not continue.
1. **Q1**: Exact HTTP request + response showing the issue RIGHT NOW? 2. **Q2**: Bug class accepted by this program? 3. **Q3**: Asset in-scope, owned by target (not third-party)? 4. **Q4**: Works without admin/privileged access? 5. **Q5**: Not documented behavior or known issue? 6. **Q6**: Impact proved with actual data (not just status code)? 7. **Q7**: Not on the never-submit list?
Never-Submit List
Missing headers (CSP/HSTS/X-Frame-Options), missing SPF/DKIM/DMARC, GraphQL introspection alone, banner/version without exploit, clickjacking without PoC, self-XSS, open redirect alone, SSRF DNS-only, CORS wildcard without credentialed exfil, logout CSRF, rate limit on non-critical, missing cookie flags alone, OAuth client_id alone, OIDC discovery endpoints, SPA client-side config.
4 Pre-Submission Gates
**Gate 0 (30 sec)**: Confirmed with real HTTP? In scope? Reproducible? Evidence?
**Gate 1 (2 min)**: What does attacker walk away with? Real victim? Max 2 preconditions?
**Gate 2 (5 min)**: Searched hacktivity? Read disclosed reports? Not in changelog?
**Gate 3 (10 min)**: Title follows formula? Steps have exact HTTP? CVSS calculated?
Conditional Validity (chain required)
| Finding | Chain Needed | Without Chain | |---|---|---| | Open redirect | + OAuth code theft → ATO | KILL | | SSRF DNS-only | + internal data exfil | KILL | | CORS wildcard | + credentialed data theft | KILL | | GraphQL introspection | + auth bypass on mutations | KILL | | S3 listing | + secrets in bundles | KILL | | Prompt injection | + IDOR via chatbot | KILL |
Severity Calibration
| Impact | Severity | |---|---| | Full ATO, RCE, mass PII exfil | Critical | | Read/modify other user's private data | High | | Stored XSS in victim context | Medium-High | | Info disclosure (sensitive creds) | Medium | | Info disclosure (non-sensitive) | Low/Info |
Read more
Triage & Validation
The 7-Question Gate (applied to EVERY finding)
First NO = KILL. Do not continue.
1. **Q1**: Exact HTTP request + response showing the issue RIGHT NOW? 2. **Q2**: Bug class accepted by this program? 3. **Q3**: Asset in-scope, owned by target (not third-party)? 4. **Q4**: Works without admin/privileged access? 5. **Q5**: Not documented behavior or known issue? 6. **Q6**: Impact proved with actual data (not just status code)? 7. **Q7**: Not on the never-submit list?
Never-Submit List
Missing headers (CSP/HSTS/X-Frame-Options), missing SPF/DKIM/DMARC, GraphQL introspection alone, banner/version without exploit, clickjacking without PoC, self-XSS, open redirect alone, SSRF DNS-only, CORS wildcard without credentialed exfil, logout CSRF, rate limit on non-critical, missing cookie flags alone, OAuth client_id alone, OIDC discovery endpoints, SPA client-side config.
4 Pre-Submission Gates
**Gate 0 (30 sec)**: Confirmed with real HTTP? In scope? Reproducible? Evidence?
**Gate 1 (2 min)**: What does attacker walk away with? Real victim? Max 2 preconditions?
**Gate 2 (5 min)**: Searched hacktivity? Read disclosed reports? Not in changelog?
**Gate 3 (10 min)**: Title follows formula? Steps have exact HTTP? CVSS calculated?
Conditional Validity (chain required)
| Finding | Chain Needed | Without Chain | |---|---|---| | Open redirect | + OAuth code theft → ATO | KILL | | SSRF DNS-only | + internal data exfil | KILL | | CORS wildcard | + credentialed data theft | KILL | | GraphQL introspection | + auth bypass on mutations | KILL | | S3 listing | + secrets in bundles | KILL | | Prompt injection | + IDOR via chatbot | KILL |
Severity Calibration
| Impact | Severity | |---|---| | Full ATO, RCE, mass PII exfil | Critical | | Read/modify other user's private data | High | | Stored XSS in victim context | Medium-High | | Info disclosure (sensitive creds) | Medium | | Info disclosure (non-sensitive) | Low/Info |
Bug bounty agent framework for Claude Code, Codex, Gemini, Cursor, Windsurf, Copilot, and OpenClaw — 48 agents, 26 commands, 19 CLI tools, 2 MCP servers, autonomous hunt loops, exploit chain builder.
Repo: H-mmer/pentest-agents
Other skills on pentest-agents.
- /analyze
Analyze recon output with AI to suggest high-value targets and attack strategies. Usage: /analyze <target>
Open skill - /autopilot
Autonomous hunt orchestrator. INSATIABLE in --autonomous mode: enforces an EXHAUSTION CONTRACT (26 canonical hunter classes, surface probe A-I, depth-engine ≥25 attempts/class, wall-clock floor 90 min/target, PRE-COMPLETION GATE before any summary). No early stops, no clarifying
Open skill - /brain
Manage the engagement brain. Subcommands: 'init' to set up, 'brief <target>' for pre-flight, 'status' for overview, 'exhausted [target]' to see dead ends.
Open skill - /chain
Build deep exploit chains — dispatches chain-builder agent. Given bug A, recursively walks the chain graph. Usage: /chain (then describe bug A)
Open skill - /correlate
Run the finding correlation engine to discover attack chains from individual findings.
Open skill - /cost
Show cost tracking and ROI for this engagement.
Open skill

