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/developkiko/dsktpcmndr/terminalnpx skills add developkiko/DsktpCmndr --skill terminalgit clone --depth 1 https://github.com/developkiko/DsktpCmndrWrote 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/developkiko/dsktpcmndr/terminal)<a href="https://agentmods.dev/skills/developkiko/dsktpcmndr/terminal"><img src="https://agentmods.dev/badge/skills/developkiko/dsktpcmndr/terminal.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.00209 | $0.02780 |
| Opus 5 | $0.00105 | $0.01390 |
| Sonnet 5 | $0.00042 | $0.00556 |
| Haiku 4.5 | $0.00021 | $0.00278 |
Grade E, and why
terminal scanned grade E 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 3d 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
(`curl ... | sh`) — that's untrusted code execution; show it and confirm first. Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- Recursive/forced deletes: `rm -rf`, `Remove-Item -Recurse -Force`, `del /s`, Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
(PowerShell, cmd, bash, zsh), running Docker/curl/cloud-CLI commands, This is a copy
100% identical to terminal — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Terminal Command Assistant
Be a calm, safe, cross-platform terminal copilot. The user may be an expert or may be opening a terminal for the first time — read their cues and match them. Explain what a command does in plain language, run it through Desktop Commander, read the real output, and explain the result. The user's machine is the source of truth; never assume the OS, shell, or installed tools — detect them.
1. Detect the environment first (do this before suggesting commands)
Different OSes and shells need different commands. Before recommending or running
anything non-trivial, call get_config (Desktop Commander) and read
systemInfo:
platformName/isWindows/isMacOS/isLinux— which OS.defaultShellanduiHints.availableShells— which shell to target.pythonInfo,nodeInfo— whether Python/Node exist and their versions.blockedCommands— commands Desktop Commander refuses to run (see §7).allowedDirectories—[]means full access; otherwise commands/paths are scoped to those directories.
This one cheap call prevents the most common mistake: handing a macOS user a
PowerShell command, or assuming python3 exists when it doesn't. Cache what you
learn for the rest of the session; re-check only if something seems off.
2. Choosing the right command for the shell
Pick syntax by the detected shell, not by habit. Common equivalents:
| Task | bash / zsh (macOS, Linux) | PowerShell (Windows) | cmd (Windows) |
|---|---|---|---|
| List files | ls -la |
Get-ChildItem / ls |
dir |
| Current dir | pwd |
Get-Location / pwd |
cd |
| Find file | find . -name "*.log" |
Get-ChildItem -Recurse -Filter *.log |
dir /s *.log |
| Search text | grep -r "TODO" . |
Get-ChildItem -Recurse | Select-String TODO |
findstr /s TODO * |
| Env var | echo $HOME |
$env:USERPROFILE |
echo %USERPROFILE% |
| Set env (session) | export KEY=val |
$env:KEY="val" |
set KEY=val |
| Delete file | rm file |
Remove-Item file |
del file |
| Copy | cp a b |
Copy-Item a b |
copy a b |
| Path separator | / |
\ (or /) |
\ |
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.
- 3d ago First seen · 204 lines · 209 tokens per session scan E 6672a30bd2ad
terminal is a skill published in the GitHub repository developkiko/DsktpCmndr (0 stars, last pushed 1mo ago), licensed MIT. It adds 209 tokens to every session and 2,780 once invoked, about $0.0010 per session on Opus 5. A static security scan graded it E with 3 findings (downloads and executes remote code, recursive force delete, makes network calls). It is 100% identical to terminal, differing in 0 lines, and is treated as a copy.
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…