metasploit-cursor-harness: Skill for Cursor

.cursor/skills/binary-exploit-pentest/SKILL.md

binary-exploit-pentest is a skill for Cursor from Suzu-Testing/metasploit-cursor-harness. It costs 49 tokens per session (1,889 once invoked), scanned A, original, MIT.

A guide for authorized exploitation research on compiled programs, including memory errors and debugging techniques.

In plain words
What is it for?
Use it on approved binaries or training challenges to inspect protections, analyze crashes, study stack or heap bugs, and build proof-of-concept exploits.
Why use it?
It provides a structured process for understanding how a vulnerable program behaves and whether its protections can be bypassed.

Skill for Cursor

Written for Cursor: installed under .cursor/.

This is Suzu-Testing/metasploit-cursor-harness's own configuration. It tells Cursor how to work on metasploit-cursor-harness itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything metasploit-cursor-harness configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Suzu-Testing/metasploit-cursor-harness. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Suzu-Testing/metasploit-cursor-harness/main/.cursor/skills/binary-exploit-pentest/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/Suzu-Testing/metasploit-cursor-harness

Made for: Cursor.

Wrote 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.

agentmods badge for binary-exploit-pentest

README.md
[![agentmods](https://agentmods.dev/badge/skills/suzu-testing/metasploit-cursor-harness/binary-exploit-pentest/github.svg)](https://agentmods.dev/skills/suzu-testing/metasploit-cursor-harness/binary-exploit-pentest)
Your own site
<a href="https://agentmods.dev/skills/suzu-testing/metasploit-cursor-harness/binary-exploit-pentest"><img src="https://agentmods.dev/badge/skills/suzu-testing/metasploit-cursor-harness/binary-exploit-pentest/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.

agentmods 80×15 button for binary-exploit-pentest

Your own site · 80×15
<a href="https://agentmods.dev/skills/suzu-testing/metasploit-cursor-harness/binary-exploit-pentest"><img src="https://agentmods.dev/badge/skills/suzu-testing/metasploit-cursor-harness/binary-exploit-pentest.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,889 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00049 $0.01889
Opus 5.5 $0.00020 $0.00756
Sonnet 5.5 $0.00010 $0.00378
Haiku 4.5 $0.00005 $0.00189

Measured 1mo ago against content hash 7f117b0e3319, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

.cursor/skills/binary-exploit-pentest/SKILL.md · 290 lines

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_check when 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')

Read the full file on GitHub · 290 lines

Changes

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.

  1. 1mo ago First seen · 290 lines · 49 tokens per session scan A 7f117b0e3319

Subscribe to this mod's changes

binary-exploit-pentest is a skill published in the GitHub repository Suzu-Testing/metasploit-cursor-harness (3 stars, last pushed 2mo ago), licensed MIT. It adds 49 tokens to every session and 1,889 once invoked, about $0.0002 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.

Related

Other skills, from other repositories

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

cwv-optimizer

Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…

adobe/skills · 112 tokens

incident-response-incident-response

Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.

rmyndharis/antigravity-skills · 36 tokens

ci-fixer

CI failures - read error, minimal fix, verify.

sipyourdrink-ltd/bernstein · 15 tokens