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/fschifone/claude-setup-wizard/setup-wizardnpx skills add fschifone/claude-setup-wizard --skill setup-wizardgit clone --depth 1 https://github.com/fschifone/claude-setup-wizardWrote 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/fschifone/claude-setup-wizard/setup-wizard)<a href="https://agentmods.dev/skills/fschifone/claude-setup-wizard/setup-wizard"><img src="https://agentmods.dev/badge/skills/fschifone/claude-setup-wizard/setup-wizard.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.00038 | $0.07170 |
| Opus 5 | $0.00019 | $0.03585 |
| Sonnet 5 | $0.00008 | $0.01434 |
| Haiku 4.5 | $0.00004 | $0.00717 |
Grade C, and why
setup-wizard scanned grade C with 2 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- Deny: rm -rf, force push, <project-specific> Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl|bash, DROP DATABASE). Recommended: yes. How it starts
The opening of the file, as written. The whole thing — 670 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Environment Setup Wizard
You are running an interactive setup wizard that produces a complete Claude Code configuration for this project. The output is a coherent set of files that make Claude token-aware, context-aware, safer, and more efficient — without imposing opinionated defaults on the user.
Prime directives
- Neutral by default. Never assume stack, style, or tooling. Ask or detect.
- One question at a time. Wait for each answer. No walls of questions.
- Detect before asking. Always inspect the repo first, skip what you can infer.
- Plan before writing. Show the complete file plan, require explicit "yes".
- Never overwrite silently. If a file exists, offer merge / backup / skip.
- Omit what's unknown. If a question is skipped, omit the section entirely
from generated files — don't write
<TBD>placeholders. A clean file with fewer sections is better than a full file with empty placeholders nobody fills in later. - Keep your replies short. This is a form, not a conversation.
Step 0 — Mode and depth selection
Argument dispatch. Normalize $ARGUMENTS first: trim whitespace, lowercase,
and strip any leading slashes or -- prefix before matching. The token agents
(also accepted: agent, --agents, -agents) is a first-class mode, not a
flag — match it BEFORE falling through to the "empty → ask mode" branch.
| Normalized token | Action |
|---|---|
agents / agent |
Run Step 1 (light detection), then jump to Step 4.5. Skip 2/3/4/5/6. |
new |
Skip detection, go to Step 2. |
existing |
Step 1 detection → Step 2. |
auto |
Step 1A deep introspection → Step 1B (0 questions). |
audit |
Step 1 detection → Step 5 (report, no writes). |
quick / full |
Set depth, then ask mode if not also given. |
| (empty) | Ask mode, then depth. |
| anything else | Treat as empty: ask mode. Do not tell the user the arg was rejected — agents is the only non----prefixed token a user is likely to type, and it's already handled above. |
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.
- 3d ago First seen · 670 lines · 38 tokens per session scan C e2916eacc934
setup-wizard is a skill published in the GitHub repository fschifone/claude-setup-wizard (2 stars, last pushed 4mo ago), licensed MIT. It adds 38 tokens to every session and 7,170 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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…