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/pentest-workflownpx skills add Suzu-Testing/metasploit-cursor-harness --skill pentest-workflowgit 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/pentest-workflow)<a href="https://agentmods.dev/skills/suzu-testing/metasploit-cursor-harness/pentest-workflow"><img src="https://agentmods.dev/badge/skills/suzu-testing/metasploit-cursor-harness/pentest-workflow.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.00071 | $0.02527 |
| Opus 5 | $0.00036 | $0.01264 |
| Sonnet 5 | $0.00014 | $0.00505 |
| Haiku 4.5 | $0.00007 | $0.00253 |
Grade A, and why
pentest-workflow 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 — 267 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pentest Workflow: Phases, Gates, Subgates
Architecture
Phase (PTES macro)
└── Gate (exit criteria before next phase)
└── Subgates (atomic tasks)
└── Skill (agent loads and executes)
└── Agent (optional delegate)
└── Skill content (self-contained techniques)
Framework synthesis:
- PTES defines 7 macro phases (state machine)
- NIST SP 800-115 allows loopback: post_exploit -> recon when new scope found
- OWASP WSTG provides web analyze/recon subgates (web_app type)
- MITRE ATT&CK tags internal post-exploit subgates (internal_ad type)
- Unified Kill Chain tracks objective depth (In / Through / Out)
Full research: frameworks.md
Configuration files
| File | Purpose |
|---|---|
engagements/catalogs/phases.yaml |
Phase definitions, gates, skill/agent routing |
engagements/catalogs/subgates-common.yaml |
Pre-engage, model, exploit, report subgates |
engagements/catalogs/subgates-web-app.yaml |
OWASP WSTG subgates |
engagements/catalogs/subgates-internal-ad.yaml |
ATT&CK subgates |
engagements/{id}/phase-state.yaml |
Current phase, completed subgates |
engagements/{id}/world-state.md |
Human-readable action log + gate/subgate status |
engagements/{id}/world-state-index.json |
Machine index for duplicate-action detection |
engagements/{id}/objectives.yaml |
Engagement objectives with status |
engagements/{id}/targets.yaml |
Prioritized targets (model phase) |
engagements/{id}/roe.yaml |
ROE + engagement_type |
Phase overview
| Phase | PTES | Gate | Primary agent | Core skills |
|---|---|---|---|---|
| pre_engage | 1 | G0 (hard) | harness-orchestrator | msf-harness |
| recon | 2 | G1 | msf-recon-agent | msf-recon, hacktricks-methodology |
| model | 3 | G2 (hard) | harness-orchestrator | pentest-knowledge-base |
| analyze | 4 | G3 | msf-recon-agent | web-app-pentest OR internal-ad-pentest |
| exploit | 5 | G4 (hard) | msf-exploit-agent | msf-exploit-chain |
| post_exploit | 6 | G5 | msf-post-agent | msf-post, internal-ad-pentest |
| report | 7 | G6 (hard) | harness-orchestrator | pentest-knowledge-base |
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 267 lines · 71 tokens per session scan A 0b804f00648f
pentest-workflow is a skill published in the GitHub repository Suzu-Testing/metasploit-cursor-harness (3 stars, last pushed 12d ago), licensed MIT. It adds 71 tokens to every session and 2,527 once invoked, about $0.0004 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…
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…