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 skills add allsmog/pwn-claude-plugin --skill dynamic-analysisgit 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/skills/allsmog/pwn-claude-plugin/dynamic-analysis)<a href="https://agentmods.dev/skills/allsmog/pwn-claude-plugin/dynamic-analysis"><img src="https://agentmods.dev/badge/skills/allsmog/pwn-claude-plugin/dynamic-analysis.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.00085 | $0.02149 |
| Opus 5 | $0.00043 | $0.01074 |
| Sonnet 5 | $0.00017 | $0.00430 |
| Haiku 4.5 | $0.00009 | $0.00215 |
Grade A, and why
PWN Dynamic Analysis scanned grade A 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 7d 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.
Asks for rootlowPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
echo 0 | sudo tee /proc/sys/kernel/randomize_va_space Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 385 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PWN Dynamic Analysis
Overview
Dynamic analysis involves running the binary under a debugger to observe behavior, calculate offsets, identify crash points, and understand memory layouts at runtime. This phase uses GDB with pwndbg for efficient exploitation research.
Dynamic Analysis Goals
- Verify static analysis findings
- Calculate exact offsets using cyclic patterns
- Identify register control at crash
- Find ASLR/PIE base addresses
- Detect bad characters that break payloads
- Observe stack and heap layouts
- Test exploit payloads
Step 1: GDB Setup with pwndbg
Launch GDB
# Basic launch
gdb ./binary
# With arguments
gdb --args ./binary arg1 arg2
# Attach to running process
gdb -p $(pidof binary)
Essential pwndbg Commands
| Command | Purpose |
|---|---|
checksec |
Show binary protections |
vmmap |
Show memory mappings |
telescope |
Examine stack with dereferencing |
context |
Show registers, stack, code |
cyclic 200 |
Generate cyclic pattern |
cyclic -l 0x61616168 |
Find offset from pattern |
search -s "/bin/sh" |
Find string in memory |
rop |
Find ROP gadgets |
got |
Show GOT entries |
plt |
Show PLT entries |
Step 2: Calculate Offset with Cyclic Pattern
Generate Pattern
Using pwntools:
from pwn import *
# Generate 200-byte cyclic pattern
print(cyclic(200))
Or in pwndbg:
pwndbg> cyclic 200
Find Offset from Crash
Run binary with pattern input, then check crash location:
pwndbg> run < <(cyclic 200)
# After crash, check RSP or fault address
pwndbg> cyclic -l $rsp
# Or for specific value
pwndbg> cyclic -l 0x6161616c
Pwntools Method
from pwn import *
io = process('./binary')
io.sendline(cyclic(200))
io.wait()
# Check core dump or use gdb.attach()
# core = Coredump('./core')
# offset = cyclic_find(core.rsp)
Step 3: Breakpoint Strategy
Common Breakpoints
# Function entry
b main
b vuln
# Specific address
b *0x401234
# Before dangerous function
b *gets@plt
# Before return
b *vuln+0x45 # Address of 'ret' instruction
# Conditional breakpoints
b *0x401234 if $rax == 0
What ships with it
3 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.
- 7d ago First seen · 385 lines · 85 tokens per session scan A f85262c71666
PWN Dynamic Analysis is a skill published in the GitHub repository allsmog/pwn-claude-plugin (2 stars, last pushed 6mo ago), licensed MIT. It adds 85 tokens to every session and 2,149 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
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…
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-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.
buffer-overflow-stack
Identify, exploit, and write custom payloads for classic Stack-Based Buffer Overflows in 32-bit and 64-bit applications. Use this skill when conducting exploit development, reverse engineering custom network protocols, or preparing for advanced certifications (OSCP, OSEP). Covers fuzzing, controlling EIP/RIP…
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-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…