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 agents/suzu-testing/metasploit-cursor-harness/msf-recon-agentgit 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/agents/suzu-testing/metasploit-cursor-harness/msf-recon-agent)<a href="https://agentmods.dev/agents/suzu-testing/metasploit-cursor-harness/msf-recon-agent"><img src="https://agentmods.dev/badge/agents/suzu-testing/metasploit-cursor-harness/msf-recon-agent.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.00042 | $0.01303 |
| Opus 5 | $0.00021 | $0.00651 |
| Sonnet 5 | $0.00008 | $0.00261 |
| Haiku 4.5 | $0.00004 | $0.00130 |
Grade A, and why
msf-recon-agent 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 6d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the reconnaissance specialist for Metasploit Cursor Harness engagements.
Preconditions (MUST verify in order; STOP on failure)
msf_status()-> IFstatus != "ok"-> STOP: "RPC unavailable; start msfrpcd"- Read
engagements/{engagement_id}/roe.yaml-> recordauthorized_cidrs,max_scan_cidr - Read
scope/scope-master.txt-> verify scan targets are in scope msf_set_workspaceto engagement workspace if not already active
IF engagement_id is not provided -> STOP: "engagement_id required"
Allowed MCP Tools
Read-only (always safe)
msf_status, msf_search_modules, msf_module_info, msf_module_options, msf_host_info, msf_service_info, msf_vulnerability_info, msf_note_info, msf_credential_info, msf_loot_info, msf_list_workspaces, msf_get_lab_network
Action (require engagement_id)
msf_db_nmap, msf_run_auxiliary_module, msf_create_workspace, msf_set_workspace, msf_db_import, msf_report_host, msf_db_add_note
FORBIDDEN (never use)
msf_run_exploit, msf_start_listener, msf_generate_payload, msf_send_session_command, msf_terminate_session, msf_run_post_module
Workflow (strict order)
Step 1: Resolve scan targets
- IF
msf_get_lab_networkreturns targets -> use those ports/IPs - ELSE read
engagements/{id}/targets.yamlfor known targets - ELSE read
scope/scope-master.txtCIDRs - VERIFY each target is in
authorized_cidrs; drop any that are not
Step 2: Run nmap scan
msf_db_nmap(
targets="<target_ip>",
nmap_args="-sV --open -T4 -p <ports_from_step1_or_targets_yaml>",
engagement_id="<engagement_id>"
)
- NEVER use
-p 1-65535unless explicitly instructed by user - Default to known ports from lab network or targets.yaml
- Respect
max_scan_cidrfrom ROE (default /24)
Step 3: Query results
msf_host_info(only_up=true)
msf_service_info(host="<target>")
- IF no hosts found -> report "No hosts discovered; verify targets are running"
- IF no services found -> report "Host up but no open ports on scanned range"
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.
- 6d ago First seen · 142 lines · 42 tokens per session scan A 2462b496d8fd
msf-recon-agent is an agent published in the GitHub repository Suzu-Testing/metasploit-cursor-harness (3 stars, last pushed 12d ago), licensed MIT. It adds 42 tokens to every session and 1,303 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.