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/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)<a href="https://agentmods.dev/commands/allsmog/pwn-claude-plugin/pwn"><img src="https://agentmods.dev/badge/commands/allsmog/pwn-claude-plugin/pwn.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.00016 | $0.00892 |
| Opus 5 | $0.00008 | $0.00446 |
| Sonnet 5 | $0.00003 | $0.00178 |
| Haiku 4.5 | $0.00002 | $0.00089 |
Grade A, and why
pwn 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 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.
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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PWN - Full Exploitation Methodology
Execute the complete binary exploitation workflow on a target binary. This command runs through all 5 phases sequentially with confirmation between each phase.
Workflow Phases
- Environment Setup - Verify tools and create workspace
- Reconnaissance - Binary analysis, protections, strings, symbols
- Static Analysis - Disassembly, vulnerable functions, buffer sizes
- Dynamic Analysis - GDB debugging, offset calculation, crash analysis
- Exploit Development - Technique selection, payload construction
Execution Steps
Step 1: Parse Arguments
Extract binary path and optional arguments:
<binary>- Required: Path to target binary--remote host:port- Optional: Remote target for final exploit--libc path- Optional: Path to libc file
If no binary specified, ask user to provide one.
Step 2: Environment Verification
Before starting analysis:
-
Check binary exists and is executable:
file <binary> -
Verify essential tools are available:
which gdb checksec python3 python3 -c "from pwn import *" -
Create workspace if needed:
mkdir -p pwn_workspace
Step 3: Execute Phases Sequentially
For each phase, use the corresponding skill and produce output in this format:
## [Phase Name]
### Findings
- Key observations as bullet points
### Commands Run
- Actual commands executed with relevant output
### Implications
- What findings mean for exploitation
### Next Steps
- Recommended actions
After each phase, ask user: "Phase complete. Continue to [next phase]?"
Step 4: Phase-Specific Instructions
Phase 1: Environment Setup
- Load
environment-setupskill - Verify tools, report missing ones
- Auto-install missing pip packages if user approves
Phase 2: Reconnaissance
- Load
reconnaissanceskill - Run:
file,checksec,strings,nm - Document architecture and protections
Phase 3: Static Analysis
- Load
static-analysisskill - Disassemble main and vulnerable functions
- Identify dangerous function calls
- Calculate buffer sizes from disassembly
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 · 147 lines · 16 tokens per session scan A b72868d502a3
pwn is a command published in the GitHub repository allsmog/pwn-claude-plugin (2 stars, last pushed 6mo ago), licensed MIT. It adds 16 tokens to every session and 892 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-web
Comprehensive web application testing for HTTP/HTTPS services. Includes directory fuzzing, vulnerability scanning, technology fingerprinting, and common exploit checks. Use this when a web service is discovered.