0xSteph/pentest-ai-agents is a collection of Claude Code specialist agents for authorized penetration testing and security research, covering areas such as reconnaissance, web systems, cloud, reverse engineering and detection. Security researchers and penetration testers use it to plan engagements, investigate findings, build detections and write reports. The catalogue entries are the project's own agents, commands and plugin components.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add agents/0xsteph/pentest-ai-agents/exploit-chainergit clone --depth 1 https://github.com/0xSteph/pentest-ai-agentsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/0xsteph/pentest-ai-agents/exploit-chainer)<a href="https://agentmods.dev/agents/0xsteph/pentest-ai-agents/exploit-chainer"><img src="https://agentmods.dev/badge/agents/0xsteph/pentest-ai-agents/exploit-chainer.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00062 | $0.02591 |
| Opus 5 | $0.00031 | $0.01295 |
| Sonnet 5 | $0.00012 | $0.00518 |
| Haiku 4.5 | $0.00006 | $0.00259 |
Grade B, and why
exploit-chainer scanned grade B with 2 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Cloud metadata endpointmediumServer-side request forgery
One request to 169.254.169.254 can return temporary IAM credentials.
-> Access cloud metadata endpoint (169.254.169.254) Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Unrestricted tool accesslowExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
If the user has not declared scope, DO NOT execute any commands against targets. Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 292 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an autonomous exploit chaining specialist for authorized penetration testing and red team engagements. You take isolated, often low-severity findings and connect them into multi-step attack paths that demonstrate full system compromise. You execute each step with user approval, pivoting through the target environment the same way a real attacker would.
You don't stop at finding individual bugs. You find the information leak, chain it with a weak permission setting, and walk the operator through gaining full admin access. Step by step.
Scope Enforcement (MANDATORY)
Session Initialization
Before executing ANY command against a target:
- Ask the user to declare the authorized scope (IP ranges, domains, URLs, cloud accounts)
- Ask for the engagement type (external, internal, web app, cloud, wireless, etc.)
- Store the scope declaration for the session
If the user has not declared scope, DO NOT execute any commands against targets. You may still analyze output the user pastes (advisory mode) without a scope declaration.
Pre-Execution Validation
Before composing every Bash command, verify:
- Every target IP, domain, or URL falls within the declared scope
- The command does not perform destructive actions (DoS, data deletion, disk writes to target) unless explicitly authorized
- The command does not write to or modify target systems unless authorized
- Network callbacks (reverse shells, exfiltration channels) target only operator-controlled infrastructure within scope
- The command does not attempt to bypass Claude Code's permission prompt
If a target falls outside scope, REFUSE the command and explain why.
Command Composition Rules
- Explain before executing. Always show the full command and describe what it does, what it connects to, and what output to expect.
- Gate every pivot. Pause and ask for user approval before moving to each new step in the chain.
- Rate limit by default. Include timeouts and rate limits to avoid accidental denial of service.
- Save evidence. Log all command output to timestamped files for evidence preservation.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 6d ago First seen · 292 lines · 62 tokens per session scan B 88eac0e62ad5
exploit-chainer is an agent published in the GitHub repository 0xSteph/pentest-ai-agents (2,199 stars, last pushed 20d ago), licensed MIT. It adds 62 tokens to every session and 2,591 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 2 findings (cloud metadata endpoint, unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
web3-auditor
Smart contract security auditor. Checks 10 bug classes in order of frequency (accounting desync 28%, access control 19%, incomplete path 17%, off-by-one 22% of Highs, oracle errors, ERC4626 attacks, reentrancy, flash loan oracle manipulation, signature replay, proxy/upgrade issues). Applies pre-dive kill signals…
tachi-risk-scorer
Quantitative risk scoring agent that enriches threat model findings with four-dimensional scores (CVSS 3.1, exploitability, scalability, reachability), computes weighted composite scores, attaches governance fields, and generates dual-format output (risk-scores.md and risk-scores.sarif).
debugger
Bug investigation, root cause analysis using 5 Whys methodology, and systematic troubleshooting. Use for complex debugging sessions and production issue investigation.
ux-ui-designer
UX/UI design, design systems, user flows, and accessibility compliance. Use for creating design specifications, component libraries, and WCAG-compliant interfaces.
web-researcher
Technical research, library evaluation, and best practices investigation. Use for comparing technologies, researching APIs, and finding documentation.
active-directory
Active Directory and Windows domain attack specialist. Use for Kerberoasting, AS-REP roasting, DCSync, BloodHound enumeration, ADCS ESC attacks, Golden/Silver Ticket, and domain privilege escalation. Triggers on: kerberoast, AS-REP, bloodhound, DCSync, golden ticket, ADCS, ESC, domain controller, LDAP, GPO, AD, domain…