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 skills add Encod3d-Sec/TORCH --skill arsenalgit 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/arsenal)<a href="https://agentmods.dev/skills/encod3d-sec/torch/arsenal"><img src="https://agentmods.dev/badge/skills/encod3d-sec/torch/arsenal/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/encod3d-sec/torch/arsenal"><img src="https://agentmods.dev/badge/skills/encod3d-sec/torch/arsenal.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high YARA Match · line 3 YARA rule matched a hack tool or exploit indicator (offensive tools, reconnaissance, privilege escalation, or exploit frameworks).Fix: Remove offensive tool references and exploit code. Legitimate agent skills should not contain penetration testing tools, exploit frameworks, or reconnaissance utilities.
- high YARA Match · line 31 YARA rule matched a hack tool or exploit indicator (offensive tools, reconnaissance, privilege escalation, or exploit frameworks).Fix: Remove offensive tool references and exploit code. Legitimate agent skills should not contain penetration testing tools, exploit frameworks, or reconnaissance utilities.
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.00244 | $0.01191 |
| Opus 5.5 | $0.00098 | $0.00476 |
| Sonnet 5.5 | $0.00049 | $0.00238 |
| Haiku 4.5 | $0.00024 | $0.00119 |
Grade A, and why
arsenal 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.
for the service? Use it; do not hand-roll a curl/socket loop. `ls wiki/tools/` for all 64. How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Arsenal
Wiki-first router. On any surface/service/vuln, get the documented TOOL and PAYLOAD from the wiki BEFORE hand-rolling or recalling from memory. The lookup itself is delegated to the fast parallel engine:
-> Skill(wiki-arsenal) - quick by default (one qmd search across all four areas, cheap, fire
it constantly); say "deep" / "full arsenal" for the 4-parallel-agent synthesized + cached card. It
covers wiki/tools + wiki/payloads + wiki/techniques + wiki/cheatsheets and returns the tool +
payload + technique + commands.
The tables below are the at-a-glance index of what wiki-arsenal pulls from - use them to
sanity-check its result, not as a substitute for the lookup. Order: automated tool -> technique -> capture.
1. Tool first (from wiki/tools/ - don't improvise)
A service/surface is fingerprinted -> reach for the tool we already document for it. Have a tool
for the service? Use it; do not hand-roll a curl/socket loop. ls wiki/tools/ for all 64.
| Surface / service | Automated tools (wiki/tools/<name>.md) |
|---|---|
| Web HTTP(S) | httpx, whatweb, nikto -> ffuf/feroxbuster/gobuster (content) -> katana/gau (crawl) -> arjun (params) -> nuclei (CVE/misconfig) -> dalfox (XSS) -> wpscan (WP); gowitness, burp-suite/burp-mcp |
| Ports / host | nmap, rustscan, naabu |
| DNS / subdomains | subfinder, amass, dnsx, gau |
| SMB / Windows / AD | netexec, responder, impacket, bloodhound/powerview, kerbrute, certipy/rubeus, evil-winrm |
| Login / creds | hydra, medusa (brute) -> hashcat, john (crack) -> jwt_tool (JWT) -> swaks (SMTP) |
| Post-shell privesc | pspy + linpeas/peass (ALWAYS, first) |
| Pivot / tunnel | chisel, ligolo-ng |
| Cloud | pacu, scoutsuite, roadtools, trivy |
| Binary / RE / pwn | ghidra, radare2, gdb-gef, pwntools, angr, binwalk, jadx, apktool, frida |
| Secrets / SAST / forensics | trufflehog, trivy, semgrep, codeql, volatility, tshark |
Read the tool page for the exact flags before running; no page -> qmd_query/Skill(wiki).
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 · 57 lines · 244 tokens per session scan A 625d16a505db
arsenal is a skill published in the GitHub repository Encod3d-Sec/TORCH (336 stars, last pushed 1mo ago), licensed MIT. It adds 244 tokens to every session and 1,191 once invoked, about $0.0010 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-30.
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…