metasploit-cursor-harness: Skill for Cursor

.cursor/skills/msf-exploit-chain/SKILL.md

msf-exploit-chain is a skill for Cursor from Suzu-Testing/metasploit-cursor-harness. It costs 69 tokens per session (3,144 once invoked), scanned A, original, MIT.

A guided workflow for using Metasploit, a security-testing toolkit, through connected coding-agent tools. It covers checking modules, running approved tests, handling sessions, and post-test actions under engagement rules.

In plain words
What is it for?
For authorized lab or security engagements that need reconnaissance, vulnerability checks, exploit tests, payload setup, session management, and post-exploitation work.
Why use it?
It keeps penetration-test steps organized and checks them against the allowed scope and rules of engagement. It also prevents unsafe defaults such as guessing the address used by reverse connections.

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/msf-exploit-chain/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 msf-exploit-chain

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/suzu-testing/metasploit-cursor-harness/msf-exploit-chain"><img src="https://agentmods.dev/badge/skills/suzu-testing/metasploit-cursor-harness/msf-exploit-chain.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 69 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,144 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.00069 $0.03144
Opus 5.5 $0.00028 $0.01258
Sonnet 5.5 $0.00014 $0.00629
Haiku 4.5 $0.00007 $0.00314

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

Security

Grade A, and why

msf-exploit-chain 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/msf-exploit-chain/SKILL.md · 368 lines

How it starts

The opening of the file, as written. The whole thing — 368 lines — stays where its author put it; the contents beside it link to each section on GitHub.

MSF Exploit Chain

Harness context

  • MCP server: msf-harness (see .cursor/mcp.json)
  • ROE configs: engagements/{id}/roe.yaml
  • Scope: scope/scope-master.txt
  • Server-side enforcement: msf_harness/mcp/policy/roe.py
  • DoS modules (auxiliary/dos/*) are blocked unconditionally

Default engagement id for lab: lab-default

LHOST Resolution (mandatory before any reverse payload)

Resolve LHOST deterministically. Try in this order; use the FIRST that succeeds:

  1. msf_get_lab_network() -> use lhost field from response
  2. Read engagements/{engagement_id}/lhost.yaml -> use lhost value
  3. STOP and ask user for LHOST IP

NEVER hardcode an IP. NEVER use 0.0.0.0. NEVER guess.

Tool inventory

Read (no ROE gate): msf_status, msf_search_modules, msf_module_info, msf_host_info, msf_service_info, msf_vulnerability_info, msf_note_info, msf_credential_info, msf_loot_info, msf_list_active_sessions, msf_list_payloads, msf_compatible_payloads, msf_list_listeners, msf_route_list

Action (require engagement_id): msf_module_check, msf_run_exploit, msf_run_auxiliary_module, msf_run_post_module, msf_send_session_command, msf_generate_payload, msf_start_listener, msf_stop_job, msf_cleanup_jobs, msf_wait_for_session, msf_session_upgrade, msf_session_sysinfo, msf_session_getuid, msf_session_ps, msf_session_download, msf_session_upload, msf_terminate_session, msf_db_nmap, msf_route_add, msf_route_delete, msf_autoroute, msf_report_host, msf_credential_add

Standard chain

Task Progress:
- [ ] msf_status - confirm RPC up
- [ ] Recon - msf_host_info / msf_service_info or auxiliary scanners
- [ ] Research - domain/vuln skills + msf_search_modules
- [ ] msf_module_info - required options
- [ ] msf_compatible_payloads - select payload
- [ ] msf_module_check - safe probe (mandatory before exploit)
- [ ] msf_start_listener - handler ready before exploit
- [ ] msf_run_exploit or msf_run_auxiliary_module
- [ ] msf_wait_for_session - poll for callback
- [ ] msf_session_upgrade - shell to meterpreter if needed
- [ ] msf_list_active_sessions - confirm session
- [ ] msf_run_post_module / msf_send_session_command
- [ ] msf_stop_job / msf_cleanup_jobs / msf_terminate_session - cleanup
- [ ] Evidence to evidence/msf/

Read the full file on GitHub · 368 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 · 368 lines · 69 tokens per session scan A 9fa1ca1c84a3

Subscribe to this mod's changes

msf-exploit-chain is a skill published in the GitHub repository Suzu-Testing/metasploit-cursor-harness (3 stars, last pushed 2mo ago), licensed MIT. It adds 69 tokens to every session and 3,144 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.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens