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/fixnpx skills add fschifone/claude-setup-wizard --skill fixgit 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/fix)<a href="https://agentmods.dev/skills/fschifone/claude-setup-wizard/fix"><img src="https://agentmods.dev/badge/skills/fschifone/claude-setup-wizard/fix.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.00034 | $0.02776 |
| Opus 5 | $0.00017 | $0.01388 |
| Sonnet 5 | $0.00007 | $0.00555 |
| Haiku 4.5 | $0.00003 | $0.00278 |
Grade C, and why
fix scanned grade C 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
! No deny list — rm -rf and force push not blocked How it starts
The opening of the file, as written. The whole thing — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Config Fix
You are a diagnostic tool that deeply analyzes an existing project and its Claude Code configuration, identifies problems, and fixes them — with user approval for each change.
This is NOT the setup wizard. This is for projects that already have some Claude config but Claude isn't performing well. You figure out why.
How you work
- Deep scan — read actual source code, not just config file names
- Diagnose — find mismatches between the project and its Claude config
- Propose fixes — show each fix clearly, get approval before writing
- Apply — make targeted edits, never rewrite from scratch
Phase 1 — Deep project introspection
Read these files to understand the project deeply. Do NOT ask the user questions you can answer by reading the code.
1.1 · Project identity & stack
Read: README.md (full), package.json, pyproject.toml, Cargo.toml, go.mod,
composer.json, Gemfile, pom.xml, build.gradle, mix.exs, pubspec.yaml
Extract: project name, description, languages, frameworks, dependencies.
1.2 · Commands & scripts
Read: package.json scripts, Makefile targets, pyproject.toml scripts,
Cargo.toml, Taskfile.yml, justfile, Procfile, docker-compose*.yml
Detect: test command, lint command, build command, dev command, deploy command,
migration command
1.3 · Architecture
Scan: top-level directory structure (ls -la, 2 levels deep)
Read: any docs/ or docs/*.md files (architecture docs)
Detect: monorepo vs single-app, frontend/backend split, microservices,
major sub-modules, entry points
1.4 · Code conventions
Scan: git log --oneline -20 (commit style)
Detect: .editorconfig, .prettierrc*, .eslintrc*, .stylelintrc*,
pyproject.toml [tool.ruff/black/isort], .rubocop.yml, .golangci.yml
Read: a few source files to detect patterns (type hints, docstrings,
import style, error handling patterns)
1.5 · Existing Claude config
Read: CLAUDE.md (full content)
Read: .claude/settings.json (full)
Read: .claude/settings.local.json (if exists)
Scan: .claude/skills/*/SKILL.md, .claude/commands/*.md, .claude/agents/*.md
Scan: .claude/hooks/*.sh
Scan: .claude/rules/*.md
Read: .mcp.json (if exists)
Read: .gitignore (check protections)
What ships with it
1 file 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 · 287 lines · 34 tokens per session scan C d9c4f89836c2
fix is a skill published in the GitHub repository fschifone/claude-setup-wizard (2 stars, last pushed 4mo ago), licensed MIT. It adds 34 tokens to every session and 2,776 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). 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…