analyze
Analyze recon output with AI to suggest high-value targets and attack strategies. Usage: /analyze <target>
Create a new engagement workspace. Usage: /new <platform> <program> [--type web-app|api|mobile|smart-contract]
$ npx -y skills add H-mmer/pentest-agents --skill new --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/newContext preview
The summary Claude sees to decide when to auto-load this skill.
Create a new engagement workspace. Usage: /new <platform> <program> [--type web-app|api|mobile|smart-contract]
name: new description: "Create a new engagement workspace. Usage: /new <platform> <program> [--type web-app|api|mobile|smart-contract]" disable-model-invocation: false
Create a new engagement workspace: $ARGUMENTS
Parse arguments as: <platform> <program> [--type <template>] Default template: web-app
Run: `uv run python3 $CLAUDE_PROJECT_DIR/tools/scaffold.py $ARGUMENTS`
After creation, tell the user to: cd into the workspace, start claude, and run /sync.
A new workspace is not ready until it can support evidence-grade hunting.
After scaffold, verify or create:
Warn if the program type needs special setup: mobile test device, API tokens, sandbox tenant, OAuth app, webhook receiver, cloud account, or smart-contract fork.
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
Analyze recon output with AI to suggest high-value targets and attack strategies. Usage: /analyze <target>
Autonomous hunt orchestrator. INSATIABLE in --autonomous mode: enforces an EXHAUSTION CONTRACT (26 canonical hunter classes, surface probe A-I, depth-engine…
Manage the engagement brain. Subcommands: 'init' to set up, 'brief <target>' for pre-flight, 'status' for overview, 'exhausted [target]' to see dead ends.
Build deep exploit chains — dispatches chain-builder agent. Given bug A, recursively walks the chain graph. Usage: /chain (then describe bug A)
Run the finding correlation engine to discover attack chains from individual findings.