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/msf-exploit-chainnpx skills add Suzu-Testing/metasploit-cursor-harness --skill msf-exploit-chaingit clone --depth 1 https://github.com/Suzu-Testing/metasploit-cursor-harnessWrote 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/suzu-testing/metasploit-cursor-harness/msf-exploit-chain)<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="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.00069 | $0.03144 |
| Opus 5 | $0.00034 | $0.01572 |
| Sonnet 5 | $0.00014 | $0.00629 |
| Haiku 4.5 | $0.00007 | $0.00314 |
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 5d 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 — 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:
msf_get_lab_network()-> uselhostfield from response- Read
engagements/{engagement_id}/lhost.yaml-> uselhostvalue - 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/
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.
- 5d ago First seen · 368 lines · 69 tokens per session scan A 9fa1ca1c84a3
msf-exploit-chain is a skill published in the GitHub repository Suzu-Testing/metasploit-cursor-harness (3 stars, last pushed 11d ago), licensed MIT. It adds 69 tokens to every session and 3,144 once invoked, about $0.0003 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.
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…