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/hacktricks-methodologynpx skills add Suzu-Testing/metasploit-cursor-harness --skill hacktricks-methodologygit 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/hacktricks-methodology)<a href="https://agentmods.dev/skills/suzu-testing/metasploit-cursor-harness/hacktricks-methodology"><img src="https://agentmods.dev/badge/skills/suzu-testing/metasploit-cursor-harness/hacktricks-methodology.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 | $0.00042 | $0.03260 |
| Opus 5 | $0.00021 | $0.01630 |
| Sonnet 5 | $0.00008 | $0.00652 |
| Haiku 4.5 | $0.00004 | $0.00326 |
Grade A, and why
hacktricks-methodology 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 4d 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 http://<target>:2375/version How it starts
The opening of the file, as written. The whole thing — 491 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Service Methodology
When to Use
- A port or service was discovered (nmap, MSF scan, client intel).
- You need service-specific attack paths, not generic web vuln payloads (use
web-app-pentestfor OWASP testing). - You need OS privesc checklists after shell access (route to OS skills).
Workflow
Task Progress:
- [ ] Identify service/version from scan or msf_service_info
- [ ] Route to dedicated skill or per-port module table below
- [ ] Enumerate with safe scanners first
- [ ] Execute in-scope only with engagement_id
Port-to-skill routing
| Port / service | Dedicated skill |
|---|---|
| 445, 139 SMB | smb-pentest |
| 389, 636 LDAP | ldap-pentest |
| 88 Kerberos | internal-ad-pentest |
| 1433 MSSQL | database-pentest |
| 3389 RDP | rdp-pentest |
| 22 SSH | ssh-pentest |
| 21 FTP | ftp-pentest |
| 25, 587 SMTP | smtp-pentest |
| 53 DNS | dns-pentest |
| 161, 162 SNMP | snmp-pentest |
| 5900 VNC | vnc-pentest |
| 5985, 5986 WinRM | winrm-pentest |
| 2049 NFS | nfs-pentest |
| 23 Telnet | telnet-pentest |
| 11211 Memcache | memcache-pentest |
| 80, 443 HTTP | web-app-pentest (+ vuln skills) |
| 3306 MySQL | database-pentest |
| 5432 PostgreSQL | database-pentest |
| 6379 Redis | database-pentest |
| 27017 MongoDB | database-pentest |
| 9200 Elasticsearch | database-pentest |
| 2375, 2376 Docker API | container-devops-pentest |
| 6443, 10250 K8s | container-devops-pentest |
Post-shell routing: Windows -> windows-pentest, Linux -> linux-pentest, macOS -> macos-pentest, domain -> internal-ad-pentest.
Per-port MSF module table
Each row: MSF MCP call (preferred) plus CLI fallback.
SMB (445/139)
MSF MCP (preferred):
msf_run_auxiliary_module(
module_name="auxiliary/scanner/smb/smb_version",
engagement_id="<id>",
options={"RHOSTS": "<target>"}
)
msf_run_auxiliary_module(
module_name="auxiliary/scanner/smb/smb_enumshares",
engagement_id="<id>",
options={"RHOSTS": "<target>", "SMBUser": "guest", "SMBPass": ""}
)
msf_run_auxiliary_module(
module_name="auxiliary/scanner/smb/smb_login",
engagement_id="<id>",
options={"RHOSTS": "<target>", "SMBUser": "admin", "SMBPass": "password"}
)
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.
- 4d ago First seen · 491 lines · 42 tokens per session scan A 629554ade024
hacktricks-methodology is a skill published in the GitHub repository Suzu-Testing/metasploit-cursor-harness (3 stars, last pushed 10d ago), licensed MIT. It adds 42 tokens to every session and 3,260 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…