Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add allsmog/pwn-claude-plugin/plugin install pwn-htbWrote 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/skills/allsmog/pwn-claude-plugin/environment-setup)<a href="https://agentmods.dev/skills/allsmog/pwn-claude-plugin/environment-setup"><img src="https://agentmods.dev/badge/skills/allsmog/pwn-claude-plugin/environment-setup/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/allsmog/pwn-claude-plugin/environment-setup"><img src="https://agentmods.dev/badge/skills/allsmog/pwn-claude-plugin/environment-setup.svg" alt="Reviewed on agentmods" width="80" 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.00071 | $0.01253 |
| Opus 5.5 | $0.00028 | $0.00501 |
| Sonnet 5.5 | $0.00014 | $0.00251 |
| Haiku 4.5 | $0.00007 | $0.00125 |
Grade A, and why
PWN Environment Setup 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 2mo 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 — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PWN Environment Setup
Overview
This skill provides methodology for setting up a complete binary exploitation environment, including tool detection, automatic installation of missing dependencies, and workspace organization for exploit development.
Required Tools
Core Tools (Must Have)
| Tool | Purpose | Installation |
|---|---|---|
| pwntools | Exploit development framework | pip install pwntools |
| gdb | Debugger | System package manager |
| pwndbg | GDB enhancement | git clone https://github.com/pwndbg/pwndbg |
| checksec | Binary protection checker | Via pwntools or apt install checksec |
Recommended Tools
| Tool | Purpose | Installation |
|---|---|---|
| ROPgadget | ROP gadget finder | pip install ROPgadget |
| ropper | Alternative gadget finder | pip install ropper |
| one_gadget | Libc one-shot gadgets | gem install one_gadget |
| seccomp-tools | Seccomp filter analyzer | gem install seccomp-tools |
| radare2 | Disassembler/debugger | System package manager |
Environment Verification Process
Step 1: Check Python Environment
Verify Python 3.8+ is available:
python3 --version
Check if pwntools is installed and functional:
python3 -c "from pwn import *; print(f'pwntools {pwnlib.version.__version__}')"
Step 2: Check GDB and Extensions
Verify GDB is installed:
gdb --version
Check for pwndbg by looking for its initialization:
gdb -q -ex "show configuration" -ex "quit" 2>&1 | grep -i pwndbg || echo "pwndbg not detected"
Step 3: Check Binary Analysis Tools
Run the tool verification script at ${CLAUDE_PLUGIN_ROOT}/skills/environment-setup/scripts/check-tools.sh to verify all tools.
Step 4: Auto-Install Missing Python Packages
For missing Python packages, install via pip:
pip install pwntools ROPgadget ropper
For Ruby gems (one_gadget, seccomp-tools):
gem install one_gadget seccomp-tools
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 207 lines · 71 tokens per session scan A 0fe569557306
PWN Environment Setup is a skill published in the GitHub repository allsmog/pwn-claude-plugin (2 stars, last pushed 8mo ago), licensed MIT. It adds 71 tokens to every session and 1,253 once invoked, about $0.0003 per session on Opus 5.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 skills, from other repositories
bypassing-binary-exploitation-mitigations
Methodology for identifying and defeating common binary hardening mitigations during authorized exploitation — ASLR, PIE, stack canaries, NX/DEP, and RELRO — by leaking addresses, brute-forcing entropy, abusing forked-process behavior, and selecting the right code-reuse primitive for the protections in place.
exploiting-arbitrary-write-to-execution
Methodology for converting an arbitrary-write (write-what-where) or write-anything-anywhere primitive into code execution during authorized engagements, covering target selection among GOT/PLT entries, .finiarray/.dtors, mallochook/freehook, the atexit/exitfuncs handler list, and printfarginfotable, plus how…
exploiting-format-string-vulnerabilities
Methodology for exploiting format string bugs where attacker-controlled data reaches the format argument of printf-family functions, enabling stack/memory disclosure (info leaks for ASLR/PIE/canary defeat) and arbitrary write primitives (%n) to hijack control flow via GOT/.finiarray overwrites.
exploiting-glibc-heap-vulnerabilities
Methodology for exploiting glibc ptmalloc2 heap vulnerabilities during authorized engagements — use-after-free, double-free, heap overflow, and bin-based attacks (tcache poisoning, fast-bin dup, unsorted/large-bin) — including modern mitigations (tcache key, safe-linking, hook removal) and how to obtain leaks and…
exploiting-integer-overflow-vulnerabilities
Methodology for finding and exploiting integer overflow, underflow, truncation, and signedness bugs in native code during authorized engagements, focusing on how wrapped arithmetic in size/length calculations leads to undersized allocations, oversized copies, length-check bypasses, and downstream heap/stack overflows.
exploiting-linux-kernel-vulnerabilities
Methodology for discovering and exploiting Linux kernel memory-corruption vulnerabilities (UAF, OOB read/write, race/TOCTOU, type confusion) during authorized engagements, covering reachability analysis, building stable read/write primitives from a single bug, defeating KASLR/SMEP/SMAP/KPTI, slab/buddy heap grooming…