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/encod3d-sec/torch/hunt-uploadnpx skills add Encod3d-Sec/TORCH --skill hunt-uploadgit clone --depth 1 https://github.com/Encod3d-Sec/TORCHWrote 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/encod3d-sec/torch/hunt-upload)<a href="https://agentmods.dev/skills/encod3d-sec/torch/hunt-upload"><img src="https://agentmods.dev/badge/skills/encod3d-sec/torch/hunt-upload.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.00048 | $0.01226 |
| Opus 5 | $0.00024 | $0.00613 |
| Sonnet 5 | $0.00010 | $0.00245 |
| Haiku 4.5 | $0.00005 | $0.00123 |
Grade A, and why
hunt-upload 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 6d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hunt: File Upload
Assumes hunt-core for the scope gate, two-account rule, confirmation gate, enumeration limits, stop conditions, wiki protocol, FIND output, and Deadends. Do not re-derive any of that here.
Wiki
qmd_query "file upload webshell extension content-type magic-byte bypass SVG XXE zip slip path traversal" via wiki-search MCP
Hub: [[web-moc]] (live index). Primary page: [[file-upload]]. Payload arsenal: wiki/payloads/file-upload.md.
Anchors: [[path-traversal-lfi]].
Attack surface
Rank the sinks first - not every upload reaches code:
- Avatar / profile / logo / signature fields - most common; frequently re-encoded, so check whether the original bytes are served back.
- Document / CSV / XML import - parser sinks (XXE, formula injection, zip).
- Ticket / message attachments - often served under the original name and type from a reachable path.
- Image-processing (thumbnails -> ImageMagick/Ghostscript), SVG/PDF render, EXIF parsers - the processor is the bug, not the store.
- Firmware / plugin / theme upload - direct code load; highest value when present.
Then attack in layers, cheapest first: extension -> content-type -> magic-byte -> parser/render.
Methodology
- Baseline: upload a valid file; note stored path, returned URL, filename transformation, and whether it is reachable + executed by the server.
- Extension bypass:
shell.php shell.phtml shell.php5 shell.phar shell.pHp
shell.php.jpg shell.jpg.php shell.php%00.jpg shell.php;.jpg
shell.php/ shell.php.... (trailing dot/space on Windows)
.htaccess -> AddType application/x-httpd-php .jpg (then upload .jpg shell)
web.config (IIS) .jsp/.jspx/.war (Java) .asp/.aspx (IIS)
- Content-Type / magic-byte bypass: set
Content-Type: image/png; prepend real magic bytes (GIF89a;,\xFF\xD8\xFFJPEG,%PDF-) before the payload; polyglot (valid image + PHP). - Path traversal in filename:
filename="../../../../var/www/html/shell.php"to escape the upload dir / overwrite files. - SVG / XML: SVG with
<script>-> stored XSS ([[xss]]); SVG/XML with external entity -> [[xxe]] (file read/SSRF). - Archive: zip-slip (
../paths inside zip) on extract; symlink in archive -> read host files. - Image processing: ImageMagick/Ghostscript (ImageTragick CVE-2016-3714), pixel-flood DoS, EXIF payload executed by a downstream parser.
- Confirm by execution, through Burp. Request the uploaded shell in Burp Repeater (operator visibility) and run a command (
?cmd=id); OOB callback if blind. For traversal, fetch the written/read target back from the path you claimed it hit. - Distill (confirmed, generic): per hunt-core,
python3 scripts/wiki-stage.py --kind technique --slug <slug> --target-page techniques/web/file-upload.md.
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.
- 6d ago First seen · 71 lines · 48 tokens per session scan A e2b763b6be8b
hunt-upload is a skill published in the GitHub repository Encod3d-Sec/TORCH (303 stars, last pushed 5d ago), licensed MIT. It adds 48 tokens to every session and 1,226 once invoked, about $0.0002 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-30.
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…
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…