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/skills/reporting-pentest/SKILL.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/skills/suzu-testing/metasploit-cursor-harness/reporting-pentest)<a href="https://agentmods.dev/skills/suzu-testing/metasploit-cursor-harness/reporting-pentest"><img src="https://agentmods.dev/badge/skills/suzu-testing/metasploit-cursor-harness/reporting-pentest/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/suzu-testing/metasploit-cursor-harness/reporting-pentest"><img src="https://agentmods.dev/badge/skills/suzu-testing/metasploit-cursor-harness/reporting-pentest.svg" alt="Reviewed on agentmods" width="80" 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.00043 | $0.01528 |
| Opus 5.5 | $0.00017 | $0.00611 |
| Sonnet 5.5 | $0.00009 | $0.00306 |
| Haiku 4.5 | $0.00004 | $0.00153 |
Grade A, and why
reporting-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 1mo 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 -s "https://www.first.org/cvss/calculator/3.1" # use web UI for vector builder How it starts
The opening of the file, as written. The whole thing — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reporting Pentest
Prerequisites
- Evidence files live under
evidence/msf/with engagement naming conventions. - Complete
pentest-workflowSG6 subgates before final delivery. - Redact credentials and PII before inclusion in reports.
Workflow
Task Progress:
- [ ] Collect findings with severity, impact, reproduction, remediation
- [ ] Link evidence files from evidence/msf/ to each finding
- [ ] Draft executive summary and severity summary
- [ ] Obfuscate secrets and PII in screenshots
- [ ] Export PDF (or Word via suzu-word MCP) for client delivery
Report structure
1. Title page (client, date, classification)
2. Executive summary (non-technical audience)
3. Scope and methodology
4. Summary of findings (severity table/chart)
5. Detailed findings (sorted by severity: Critical -> Info)
6. Remediation roadmap (prioritized)
7. Appendices (large PoCs, raw scan data, glossary)
Finding template
Each finding must include: Title, Severity/CVSS, Description, Impact, Reproduction steps, Remediation, Evidence.
| Rating | CVSS range | Criteria |
|---|---|---|
| Critical | 9.0-10.0 | Unauthenticated RCE, full domain compromise |
| High | 7.0-8.9 | Auth bypass, significant data exposure |
| Medium | 4.0-6.9 | Limited impact, requires user interaction |
| Low | 0.1-3.9 | Minor info disclosure, hard to exploit |
| Info | 0.0 | Best practice, no direct exploit |
CVSS calculation workflow
MSF: No direct module; use CLI/tools.
CLI fallback:
# CVSS v3.1 calculator (First.org API)
curl -s "https://www.first.org/cvss/calculator/3.1" # use web UI for vector builder
# cvss-cli (npm)
npm install -g cvss
cvss --base "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
# Output: 9.8 Critical
# Python cvss library
python3 -c "from cvss import CVSS3; print(CVSS3('CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N').scores)"
Vector selection guide
| Metric | Common pentest values |
|---|---|
| AV (Attack Vector) | N=network, A=adjacent, L=local |
| AC (Attack Complexity) | L=low, H=high |
| PR (Privileges Required) | N=none, L=low, H=high |
| UI (User Interaction) | N=none, R=required |
| S (Scope) | U=unchanged, C=changed |
| C/I/A | N=none, L=low, H=high |
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.
- 1mo ago First seen · 201 lines · 43 tokens per session scan A 8b950a0502b1
reporting-pentest is a skill published in the GitHub repository Suzu-Testing/metasploit-cursor-harness (3 stars, last pushed 2mo ago), licensed MIT. It adds 43 tokens to every session and 1,528 once invoked, about $0.0002 per session on Opus 5.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
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…