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 commands/allsmog/pwn-claude-plugin/pwn-exploitgit clone --depth 1 https://github.com/allsmog/pwn-claude-pluginWrote 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/commands/allsmog/pwn-claude-plugin/pwn-exploit)<a href="https://agentmods.dev/commands/allsmog/pwn-claude-plugin/pwn-exploit"><img src="https://agentmods.dev/badge/commands/allsmog/pwn-claude-plugin/pwn-exploit.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.00017 | $0.00805 |
| Opus 5 | $0.00009 | $0.00402 |
| Sonnet 5 | $0.00003 | $0.00161 |
| Haiku 4.5 | $0.00002 | $0.00081 |
Grade A, and why
pwn-exploit 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 5d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PWN Exploit - Exploit Development
Guide exploit development based on previous analysis findings.
Execution Steps
Step 1: Gather Findings
Review previous analysis to determine:
- Vulnerability type (buffer overflow, format string, etc.)
- Protections (RELRO, Canary, NX, PIE)
- Available primitives (win function, libc, gadgets)
- Calculated offsets
If findings not available, ask user for:
- Binary protections
- Vulnerability type
- Offset to return address
- Available targets (win function address, libc)
Step 2: Select Technique
Based on protections, recommend technique:
| Protections | Recommended Technique |
|---|---|
| No NX, No PIE | Shellcode injection |
| NX, No PIE, win() | ret2win |
| NX, No PIE, No win | ret2libc |
| NX, PIE | Leak + ret2libc |
| Canary present | Leak canary first |
| Full RELRO | Stack-based attack only |
If --technique flag provided, use that technique.
Otherwise, ask user to confirm recommended technique.
Step 3: Find Required Components
Based on technique:
ret2win:
nm <binary> | grep -i win
ret2libc:
# Find gadgets
ROPgadget --binary <binary> | grep "pop rdi"
# Find /bin/sh in libc
strings -t x <libc> | grep "/bin/sh"
ROP:
ROPgadget --binary <binary> --only "pop|ret"
ropper -f <binary> --search "pop rdi"
Format string: Determine offset by testing with pattern.
Step 4: Generate Exploit
Create pwntools exploit script with:
- Correct context setup
- Local/remote toggle
- GDB attach option
- Educational comments explaining each step
- All calculated values filled in
Step 5: Save and Test
Save exploit to exploit.py and provide test instructions:
# Local test
python3 exploit.py
# With GDB
python3 exploit.py GDB
# Remote
python3 exploit.py REMOTE
Output Format
## Exploit Development
### Technique Selection
- Vulnerability: Buffer overflow (gets)
- Protections: NX enabled, No PIE, No Canary
- Selected: ret2libc (no win function available)
### Required Components
- pop rdi gadget: 0x401234
- puts@plt: 0x401030
- puts@got: 0x404018
- main: 0x401150
### Exploit Strategy
1. Stage 1: Leak libc address via puts(puts@got)
2. Return to main for second input
3. Stage 2: Call system("/bin/sh") with leaked libc base
### Generated Exploit
```python
#!/usr/bin/env python3
from pwn import *
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.
- 5d ago First seen · 132 lines · 17 tokens per session scan A d9f377bc3101
pwn-exploit is a command published in the GitHub repository allsmog/pwn-claude-plugin (2 stars, last pushed 6mo ago), licensed MIT. It adds 17 tokens to every session and 805 once invoked, about $0.0001 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-31.
Other commands, from other repositories
bb-ad
Active Directory enumeration and attack techniques. Includes LDAP enumeration, Kerberos attacks (Kerberoasting, AS-REP Roasting), SMB attacks, and domain privilege escalation. Use this when targeting Windows domain environments.
bb-enum
Service-specific enumeration based on discovered ports. Automatically selects appropriate enumeration techniques for each service. Use after /bb-recon to deeply enumerate discovered services.
bb-setup
Verify penetration testing environment and tool installation. Use this before starting an HTB machine to ensure all required tools are available.
bb-crack
Crack password hashes with automatic type detection and wordlist discovery. Supports MD5, SHA, NTLM, bcrypt, and more.
bb-spray
Credential spraying across discovered services.
bb-recon
Automated network reconnaissance against a target. Runs comprehensive port scanning with nmap, identifies services, and discovers attack surface. Use this as the first step when attacking an HTB machine.