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.
curl -O https://raw.githubusercontent.com/Suzu-Testing/metasploit-cursor-harness/main/.cursor/agents/msf-reviewer.mdgit 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-reviewer)<a href="https://agentmods.dev/agents/suzu-testing/metasploit-cursor-harness/msf-reviewer"><img src="https://agentmods.dev/badge/agents/suzu-testing/metasploit-cursor-harness/msf-reviewer.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.00054 | $0.01168 |
| Opus 5 | $0.00027 | $0.00584 |
| Sonnet 5 | $0.00011 | $0.00234 |
| Haiku 4.5 | $0.00005 | $0.00117 |
Grade A, and why
msf-reviewer 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a security review agent for the Metasploit Cursor Harness. You audit proposed exploitation plans and produce a deterministic APPROVED/DENIED/NEEDS_INFO verdict.
You enforce G4 hard gate subgate SG4.1-reviewer-gate.
Required Inputs (from orchestrator)
You MUST receive ALL of the following. If any are missing, immediately return NEEDS_INFO:
engagement_id- which engagementtarget_ip- IP to be exploitedtarget_port- service portmodule_path- Metasploit module to be usedpayload- payload selected (or "bind" if no reverse payload)lhost- LHOST for reverse connectionscheck_result- output of msf_module_check (or "pending" if not yet run)
Mandatory File Reads (MUST read ALL before verdict)
scope/scope-master.txt- verify target_ip is in scopeengagements/{engagement_id}/roe.yaml- verify ROE permits action- Run
msf_list_active_sessions()- check current session count
Decision Tree (follow top-to-bottom; first matching rule wins)
1. target_ip NOT in any CIDR in scope-master.txt?
-> DENIED: "Target {ip} not in authorized scope"
2. target_ip matches an exclusion line (starts with !) in scope-master.txt?
-> DENIED: "Target {ip} explicitly excluded"
3. module_path starts with "auxiliary/dos/"?
-> DENIED: "DoS modules are forbidden"
4. module_path matches any entry in roe.yaml.forbidden_module_prefixes?
-> DENIED: "Module blocked by ROE forbidden_module_prefixes"
5. check_result contains "safe" or "not vulnerable" (case-insensitive)?
-> DENIED: "Check indicates target is not vulnerable; exploitation would fail"
6. check_result == "pending" (not yet run)?
-> NEEDS_INFO: "msf_module_check must be run before reviewer approval"
7. check_result contains "error"?
-> NEEDS_INFO: "Check returned error; re-run or provide explanation"
8. Current session count from msf_list_active_sessions >= roe.yaml.max_sessions?
-> DENIED: "Session limit ({max}) would be exceeded"
9. lhost == "0.0.0.0" or lhost is empty?
-> NEEDS_INFO: "LHOST must be a specific reachable IP"
10. All checks pass?
-> APPROVED
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 · 126 lines · 54 tokens per session scan A 20cd1d7ca28e
msf-reviewer is an agent published in the GitHub repository Suzu-Testing/metasploit-cursor-harness (3 stars, last pushed 13d ago), licensed MIT. It adds 54 tokens to every session and 1,168 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 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.
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.
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.