/learn
Record a platform response and update learning. Usage: /learn <report_id> <status> [--bounty 500] [--vuln-type XSS]
$ npx -y skills add H-mmer/pentest-agents --skill learn --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
/learn
Context preview
The summary Claude sees to decide when to auto-load this skill.
Record a platform response and update learning. Usage: /learn <report_id> <status> [--bounty 500] [--vuln-type XSS]
SKILL.md
learn.SKILL.mdname: learn description: "Record a platform response and update learning. Usage: /learn <report_id> <status> [--bounty 500] [--vuln-type XSS]" disable-model-invocation: false
Record platform response: $ARGUMENTS
1. Parse arguments and run: `uv run python3 $CLAUDE_PROJECT_DIR/tools/response_tracker.py log $ARGUMENTS` 2. Also update brain: `uv run python3 $CLAUDE_PROJECT_DIR/tools/brain.py log "Report response: $ARGUMENTS"` 3. Sync to global brain: `uv run python3 $CLAUDE_PROJECT_DIR/tools/global_brain.py sync-from-local` 4. Show updated insights: `uv run python3 $CLAUDE_PROJECT_DIR/tools/response_tracker.py insights`
Top-Tier Learning Loop
Convert every platform response into a future hunting rule.
- If accepted: record the decisive proof artifact, impact framing, asset type, vuln variant, bounty tier, and why triage agreed.
- If duplicate: record the duplicated primitive and which uniqueness signal was missing.
- If N/A: record the exact sentence or policy clause that killed it.
- If informative: record the missing chain or business impact required to make it payable.
- If severity changed: record the evidence that moved it up or down.
End with one concrete update: a brain pattern, a never-submit rule, a report wording change, or a target ranking adjustment.
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

