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/diegomarino/claude-toolshed/dev-setupnpx skills add diegomarino/claude-toolshed --skill dev-setupgit clone --depth 1 https://github.com/diegomarino/claude-toolshedWhat 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.00021 | $0.07066 |
| Opus 5 | $0.00010 | $0.03533 |
| Sonnet 5 | $0.00004 | $0.01413 |
| Haiku 4.5 | $0.00002 | $0.00707 |
Grade B, and why
dev-setup scanned grade B 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 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
SKILL_DIR="$(find "$HOME/.claude/plugins/cache" -type d -name "dev-setup" -path "*/skills/dev-setup" 2>/dev/null | head -1)" The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What ships with it
17 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.
- reference/dev-allocate-ports.sh 3.2 KB runs code
- reference/dev-check-ports.sh 2.5 KB runs code
- reference/dev-chrome-profile-setup.sh 5.7 KB runs code
- reference/dev-concurrently.sh 1.8 KB runs code
- reference/dev-open-browser.sh 4.0 KB runs code
- reference/dev-post-checkout.sh 2.5 KB runs code
- reference/dev-read-ports.sh 2.1 KB runs code
- reference/dev-restart-all-servers.sh 800 B runs code
- reference/dev-servers-status.sh 3.1 KB runs code
- reference/dev-session-name.sh 915 B runs code
- reference/dev-setup-health.sh 1.4 KB runs code
- reference/dev-stop-all-servers.sh 2.9 KB runs code
- reference/dev-tmux-start.sh 4.8 KB runs code
- reference/dev-tmux.sh 1.0 KB runs code
- reference/dev-wt-ports.sh 2.4 KB runs code
- references/upgrade-route.md 3.5 KB
- scripts/ensure-deps.sh 1.4 KB runs code
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 · 604 lines · 21 tokens per session scan B b6f675daa6eb
dev-setup is a skill published in the GitHub repository diegomarino/claude-toolshed (58 stars, last pushed 4mo ago), with no licence file. It adds 21 tokens to every session and 7,066 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). 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…