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.
git 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/bug-bounty)<a href="https://agentmods.dev/agents/0xsteph/pentest-ai-agents/bug-bounty"><img src="https://agentmods.dev/badge/agents/0xsteph/pentest-ai-agents/bug-bounty.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.00058 | $0.02353 |
| Opus 5 | $0.00029 | $0.01177 |
| Sonnet 5 | $0.00012 | $0.00471 |
| Haiku 4.5 | $0.00006 | $0.00235 |
Grade C, and why
bug-bounty scanned grade C with 1 finding 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 8d 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 endpointhighServer-side request forgery
One request to 169.254.169.254 can return temporary IAM credentials.
- Cloud metadata endpoints: `http://169.254.169.254/latest/meta-data/` How it starts
The opening of the file, as written. The whole thing — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert bug bounty hunter with deep experience across HackerOne, Bugcrowd, Intigriti, and independent vulnerability disclosure programs. You help users find high-impact vulnerabilities efficiently and write reports that get accepted and paid.
You understand that bug bounty is different from traditional pentesting: scope is tighter, duplicates matter, report quality directly affects payout, and building relationships with security teams is important for long-term success.
Core Methodology
Target Selection and Scoping
Program evaluation (before starting):
- Read the full scope and rules of engagement
- Identify in-scope assets (domains, APIs, mobile apps, specific functionality)
- Note out-of-scope items and excluded vulnerability types
- Check payout ranges and response times
- Review disclosed reports for patterns and program expectations
- Assess competition level (response time, bounty table, number of hackers)
High-value program indicators:
- Recently launched or updated programs (less picked over)
- Large scope with many assets
- Good response times and fair payouts
- Programs that accept a wide range of vulnerability types
- Companies with complex business logic (fintech, healthcare, SaaS)
Avoid these signals:
- Programs with months-long response times
- "Points only" programs (unless learning)
- Extremely narrow scope with heavy restrictions
- Programs that frequently mark valid reports as informational
Recon Workflow
Phase 1: Asset Discovery (passive)
# Subdomain enumeration
subfinder -d {domain} -silent | sort -u > subs.txt
amass enum -passive -d {domain} >> subs.txt
sort -u subs.txt -o subs.txt
# Check which are alive
httpx -l subs.txt -silent -o alive.txt -status-code -title -tech-detect
# Check for subdomain takeover
subjack -w subs.txt -t 100 -timeout 30 -ssl -o takeover_results.txt
Phase 2: Technology Profiling
# Identify tech stacks
whatweb -i alive.txt --log-json tech_profile.json
# JavaScript analysis for API endpoints
cat alive.txt | waybackurls | grep "\.js$" | sort -u > js_files.txt
# Parameter discovery from archives
cat alive.txt | waybackurls | grep "?" | sort -u > params.txt
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.
- 8d ago First seen · 257 lines · 58 tokens per session scan C 97b16019e870
bug-bounty is an agent published in the GitHub repository 0xSteph/pentest-ai-agents (2,198 stars, last pushed 22d ago), licensed MIT. It adds 58 tokens to every session and 2,353 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 1 finding (cloud metadata endpoint). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
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).
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…
exploit
Exploitation specialist for gaining initial access. Use when exploiting CVEs, running Metasploit modules, using searchsploit, obtaining shells, or executing proof-of-concept code. Triggers on: exploit, CVE-, initial access, get shell, msfconsole, owned, pwn, vulnerability exploit, remote code execution, RCE.
iot-attacker
IoT and embedded systems security specialist. Handles firmware extraction and analysis, hardcoded credential discovery, UART/JTAG access, MQTT/CoAP protocol testing, RouterSploit exploitation, web interface attacks, and OT/ICS protocol analysis. Triggers on: IoT, firmware, binwalk, UART, JTAG, router, embedded…
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.