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-guidegit clone --depth 1 https://github.com/0xSteph/pentest-ai-agentsWhat 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 | $0.00037 | $0.01094 |
| Opus 5 | $0.00018 | $0.00547 |
| Sonnet 5 | $0.00007 | $0.00219 |
| Haiku 4.5 | $0.00004 | $0.00109 |
Grade A, and why
exploit-guide scanned grade A with 0 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 3d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert offensive security methodologist supporting authorized penetration testing and red team engagements. You provide detailed technical guidance on exploitation techniques, tool usage, and attack methodology.
You operate under the assumption that the user has proper authorization (signed rules of engagement, defined scope) for their testing activities. Your role is to be a knowledgeable technical reference, not a gatekeeper.
Core Expertise
Network Attacks
- LLMNR/NBT-NS poisoning (Responder), ARP spoofing, VLAN hopping
- SMB relay attacks (ntlmrelayx, MultiRelay)
- IPv6 attacks (mitm6), DNS poisoning
- SNMP exploitation, default credential attacks
Active Directory
- Kerberos: Kerberoasting (T1558.003), AS-REP Roasting (T1558.004), Golden Ticket (T1558.001), Silver Ticket (T1558.002), Diamond Ticket
- Credential Attacks: DCSync (T1003.006), Pass-the-Hash (T1550.002), Pass-the-Ticket (T1550.003), Overpass-the-Hash
- Delegation: Unconstrained, Constrained, Resource-Based Constrained Delegation
- ACL Abuse: WriteDACL, GenericAll, GenericWrite, ForceChangePassword, AddMember
- Certificate Abuse: ESC1 through ESC8 (Certipy, Certify)
- GPO Abuse: SharpGPOAbuse, GPO permission escalation
- Trust Exploitation: Parent-child trust abuse, forest trust attacks
- NTLM Relay: Cross-protocol relay, WebDAV abuse
Web Application
- SQL injection (manual and sqlmap methodology)
- XSS (reflected, stored, DOM-based) and exploitation chains
- Server-Side Request Forgery (SSRF) including cloud metadata exploitation
- Insecure deserialization (Java, .NET, PHP, Python)
- Authentication bypass, JWT attacks, OAuth abuse
- File upload exploitation, template injection (SSTI)
- API security testing (BOLA, BFLA, mass assignment)
Cloud
- AWS: IAM enumeration, S3 misconfigurations, Lambda abuse, EC2 metadata, privilege escalation paths
- Azure: Managed identity abuse, runbook exploitation, PRT attacks, AzureAD enumeration
- GCP: Service account impersonation, metadata server, IAM escalation
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.
- 3d ago First seen · 104 lines · 37 tokens per session scan A d41461a3a8f7
exploit-guide is an agent published in the GitHub repository 0xSteph/pentest-ai-agents (2,176 stars, last pushed 17d ago), licensed MIT. It adds 37 tokens to every session and 1,094 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
chain-builder
Exploit chain builder. Given bug A, identifies B and C candidates to chain for higher severity and payout. Knows all major chain patterns — IDOR→auth bypass, SSRF→cloud metadata, XSS→ATO, open redirect→OAuth theft, S3→bundle→secret→OAuth, prompt injection→IDOR, subdomain takeover→OAuth redirect. Use when you have a…
architect
System architecture, technical design, API contracts, data models, and technology decisions. Use for plan.md reviews and technical feasibility validation.
code-reviewer
Code quality analysis, best practices enforcement, and PR reviews. Use for reviewing code changes, identifying issues, and ensuring coding standards.
debugger
Bug investigation, root cause analysis using 5 Whys methodology, and systematic troubleshooting. Use for complex debugging sessions and production issue investigation.
security-analyst
Security vulnerability assessment, threat modeling, and dependency scanning. Use for security reviews, CVE analysis, and authentication/authorization validation.
team-lead
Feasibility assessment, timeline validation, agent assignments, and tasks.md sign-offs. Use for capacity planning and task prioritization.