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/ai-tools-setupnpx skills add developkiko/DsktpCmndr --skill ai-tools-setupgit 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/ai-tools-setup)<a href="https://agentmods.dev/skills/developkiko/dsktpcmndr/ai-tools-setup"><img src="https://agentmods.dev/badge/skills/developkiko/dsktpcmndr/ai-tools-setup.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.00168 | $0.01392 |
| Opus 5 | $0.00084 | $0.00696 |
| Sonnet 5 | $0.00034 | $0.00278 |
| Haiku 4.5 | $0.00017 | $0.00139 |
Grade A, and why
ai-tools-setup 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 2d 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.
curl to the provider) early, and tell the user plainly if the key is invalid This is a copy
98% identical to ai-tools-setup — 6 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Tools Setup Assistant
Help users install, configure, and repair AI tooling on their own machine using Desktop Commander's file and terminal tools. The work is usually configure-and-troubleshoot, not clean installs — assume something already exists and may be half-broken.
Golden rules (read before doing anything)
- Detect the OS and shell first. Read
get_configand use itssystemInfoandallowedDirectories— file paths, commands, and config locations differ across macOS, Windows, and Linux, so confirm the platform before assuming anything. - Verify the model/API key works before you build. The most common reason
these sessions dead-end is a provider auth or billing error discovered
after a lot of setup work. Make one tiny test call with
start_process(a quick curl to the provider) early, and tell the user plainly if the key is invalid or out of credit. - Translate errors, don't dump them. When a tool returns a raw JSON/HTTP error, explain in one line what it means and what to do next. If a model is missing, deprecated, rate-limited, or doesn't support tool-calling, suggest a concrete working alternative instead of retrying the same thing.
- Never echo secrets. API keys, tokens, and passwords go into the right
config or
.envfile — never repeated back in chat. If a user pastes a live secret, warn them, use it, and suggest they rotate it if it was shared insecurely. Redact secrets in any output, logs, or summaries you produce. - Back up before you edit. Copy the config to a
.bakfirst withstart_process(cp file.json file.json.bak, orcopyon Windows), then make the change withedit_blockso existing entries survive — reach forwrite_fileonly on a from-scratch config. Validate the JSON after every edit by parsing it withstart_process. - Verify, then stop. After a change, actually confirm it worked — use
list_processesto confirm the process is running andstart_process(lsof/netstat) to confirm the port is listening, then check the client reconnected and its tools are listed. Don't declare success on a guess. - Make it repeatable. Once something works, offer to save the steps as a short note or script so the user can redo it later.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 108 lines · 168 tokens per session scan A ceaa1869683c
ai-tools-setup is a skill published in the GitHub repository developkiko/DsktpCmndr (0 stars, last pushed 1mo ago), licensed MIT. It adds 168 tokens to every session and 1,392 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 98% identical to ai-tools-setup, differing in 6 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…