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/forensics-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/forensics-pentest)<a href="https://agentmods.dev/skills/suzu-testing/metasploit-cursor-harness/forensics-pentest"><img src="https://agentmods.dev/badge/skills/suzu-testing/metasploit-cursor-harness/forensics-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/forensics-pentest"><img src="https://agentmods.dev/badge/skills/suzu-testing/metasploit-cursor-harness/forensics-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.00044 | $0.01564 |
| Opus 5.5 | $0.00018 | $0.00626 |
| Sonnet 5.5 | $0.00009 | $0.00313 |
| Haiku 4.5 | $0.00004 | $0.00156 |
Grade A, and why
forensics-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.
Asks for rootlowPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo mount -o ro,loop evidence.img /mnt/evidence Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Forensics Pentest
Prerequisites
- Evidence (image, dump, pcap) is authorized and chain-of-custody documented.
- Work on copies; never modify original evidence media.
- Forensic analysis during active pentest supports finding validation and IOC extraction.
Workflow
Task Progress:
- [ ] Acquire or mount forensic image (write-blocker if hardware)
- [ ] Identify partitions, filesystem, and timeline
- [ ] Run targeted artifact extraction (registry, browser, logs)
- [ ] Analyze memory dump or pcap if available
- [ ] Document IOCs and link to reporting-pentest findings
Phase 1: Image acquisition and mounting
Disk imaging
MSF: No direct module. Use dd/dcfldd for acquisition.
CLI fallback:
dd if=/dev/sdb of=evidence.img bs=4M status=progress
dcfldd if=/dev/sdb of=evidence.img hash=sha256 hashlog=hashes.txt
sha256sum evidence.img
Mount safely (read-only)
MSF: No direct module. Use loop mount and Sleuth Kit.
CLI fallback:
sudo mount -o ro,loop evidence.img /mnt/evidence
sudo losetup -Pr /dev/loop0 evidence.img
mmls evidence.img
fls -r -o 2048 evidence.img
file evidence.img
fdisk -l evidence.img
fsstat -o 2048 evidence.img
Phase 2: File and data carving
binwalk
MSF: No direct module. Use binwalk CLI.
CLI fallback:
binwalk evidence.img
binwalk -e evidence.img
binwalk -A evidence.img
foremost -i evidence.img -o carved/
scalpel -c scalpel.conf evidence.img
exiftool -r /mnt/evidence/
Phase 3: Memory forensics
Volatility 3
MSF: No direct module. Use Volatility CLI.
CLI fallback:
vol -f memory.dmp windows.info
vol -f memory.dmp windows.pslist
vol -f memory.dmp windows.pstree
vol -f memory.dmp windows.netscan
vol -f memory.dmp windows.cmdline
vol -f memory.dmp windows.malfind
vol -f memory.dmp windows.hashdump
vol -f memory.lime linux.pslist
vol -f memory.lime linux.bash
Key memory artifacts
| Plugin | Purpose |
|---|---|
| pslist/pstree | Running processes |
| netscan/sockscan | Network connections |
| cmdline | Process command lines |
| malfind | Injected code detection |
| hashdump | NTLM hashes (Windows) |
| filescan | Open file handles |
| dlllist | Loaded DLLs |
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 · 235 lines · 44 tokens per session scan A 5979d175b4cd
forensics-pentest is a skill published in the GitHub repository Suzu-Testing/metasploit-cursor-harness (3 stars, last pushed 2mo ago), licensed MIT. It adds 44 tokens to every session and 1,564 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (asks for root). 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…