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/initial-access-pentestnpx skills add Suzu-Testing/metasploit-cursor-harness --skill initial-access-pentestgit 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/initial-access-pentest)<a href="https://agentmods.dev/skills/suzu-testing/metasploit-cursor-harness/initial-access-pentest"><img src="https://agentmods.dev/badge/skills/suzu-testing/metasploit-cursor-harness/initial-access-pentest.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.00037 | $0.02401 |
| Opus 5 | $0.00018 | $0.01201 |
| Sonnet 5 | $0.00007 | $0.00480 |
| Haiku 4.5 | $0.00004 | $0.00240 |
Grade A, and why
initial-access-pentest scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -skI https://vpn.target.com/ How it starts
The opening of the file, as written. The whole thing — 299 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Initial Access Pentest
Prerequisites
- Target is in scope (
scope/scope-master.txt, engagement ROE). - Phishing and credential spraying require explicit ROE authorization.
- Social engineering must use approved pretexts and infrastructure.
Workflow
Task Progress:
- [ ] Map external attack surface (web, VPN, email, exposed services)
- [ ] Prioritize credential and service-based entry paths
- [ ] Validate findings with safe checks before exploit delivery
- [ ] Cross-reference MSF modules after vulnerability confirmation
- [ ] Document delivery chain if phishing is in scope
Phase 1: External attack surface mapping
Web and application discovery
MSF MCP (preferred):
msf_db_nmap(
engagement_id="<id>",
targets="<target>",
nmap_args="-sV -sC -p 21,22,25,80,443,445,3389,5985,8080,8443"
)
msf_run_auxiliary_module(
module_name="auxiliary/scanner/http/http_version",
engagement_id="<id>",
options={"RHOSTS": "<target>", "RPORT": 443, "SSL": true}
)
msf_run_auxiliary_module(
module_name="auxiliary/scanner/http/dir_scanner",
engagement_id="<id>",
options={"RHOSTS": "<target>", "RPORT": 443, "SSL": true}
)
CLI fallback:
subfinder -d domain.com -o subs.txt
httpx -l subs.txt -o live.txt
whatweb -i live.txt
nuclei -l live.txt -t exposures/
gobuster dir -u https://TARGET/ -w common.txt
nmap -sS -sV -p- --open TARGET
Map: VPN portals, OWA/Exchange, Citrix, RDP gateways, admin panels, dev/staging subdomains.
VPN portal testing
MSF MCP (preferred):
msf_run_auxiliary_module(
module_name="auxiliary/scanner/http/http_login",
engagement_id="<id>",
options={"RHOSTS": "<vpn>", "RPORT": 443, "SSL": true, "TARGETURI": "/remote/login", "USERPASS_FILE": "/tmp/creds.txt"}
)
msf_search_modules(query="vpn pulse secure citrix")
CLI fallback:
# Fingerprint VPN
curl -skI https://vpn.target.com/
whatweb https://vpn.target.com/
# Credential spray (ROE throttle)
ffuf -u https://vpn.target.com/remote/login -X POST \
-d "username=FUZZ&password=Winter2026!" -w users.txt -mc 200,302
# Check for known CVEs by version
nuclei -u https://vpn.target.com -t cves/
searchsploit "pulse secure"
searchsploit "fortinet ssl vpn"
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 · 299 lines · 37 tokens per session scan A 50bd5d826d0a
initial-access-pentest is a skill published in the GitHub repository Suzu-Testing/metasploit-cursor-harness (3 stars, last pushed 12d ago), licensed MIT. It adds 37 tokens to every session and 2,401 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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…
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…
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.
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…
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…