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 skills add paulo-yamagishi/claude-code-setup --skill skillgit clone --depth 1 https://github.com/paulo-yamagishi/claude-code-setupWrote 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/paulo-yamagishi/claude-code-setup/skill)<a href="https://agentmods.dev/skills/paulo-yamagishi/claude-code-setup/skill"><img src="https://agentmods.dev/badge/skills/paulo-yamagishi/claude-code-setup/skill.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.1 | $0.00012 | $0.03342 |
| Opus 5 | $0.00006 | $0.01671 |
| Sonnet 5 | $0.00002 | $0.00668 |
| Haiku 4.5 | $0.00001 | $0.00334 |
Grade B, and why
setup scanned grade B 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 8d 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 directorieslowAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- Settings: `.claude/settings.json` (project), `.claude/settings.local.json` (personal), `~/.claude/settings.json` (user) Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Recursive force deletemediumDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- **Settings**: Detected test/lint/build → permissions.allow. Standard deny rules for rm -rf, DROP, --force. Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
This is a copy
100% identical to setup — 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 — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Setup Advisor
You are auditing the current project's Claude Code configuration. Follow these phases in order.
1. Routing
Parse $ARGUMENTS to determine scope:
- Empty or unrecognized → full audit (all 11 categories)
quick→ full audit but only show IMPROVE and MISSING items, skip GOOD- Category name → audit only that category:
claude-md,settings,hooks,skills,agents,mcp,rules,plugins,sandbox,model,styles
2. Detection
Silently scan the project. Do NOT dump raw file contents to the user.
Project stack: Read package.json, pyproject.toml, Cargo.toml, go.mod, pom.xml, Gemfile, composer.json (whichever exists). Note: language, framework, package manager.
Tools: Check for formatters (.prettierrc*, [tool.black], .rustfmt.toml, biome.json/biome.jsonc), linters (.eslintrc*, eslint.config.*, [tool.ruff], .golangci.yml, biome.json/biome.jsonc), test runners (test script in package.json, [tool.pytest], *_test.go), lockfiles.
Existing Claude config: Check for .claude/ directory, CLAUDE.md, .claude/settings.json, .claude/settings.local.json, .claude/skills/, .claude/agents/, .claude/rules/, .claude/output-styles/, .mcp.json. Check settings for enabledPlugins, sandbox, model, effortLevel, outputStyle.
Git: Check for .git/, remote origin URL (git config --get remote.origin.url), contributor count (git shortlog -sn --no-merges | wc -l).
Workflow triggers: CI/CD (.github/workflows/, .gitlab-ci.yml, Jenkinsfile), deploy (Dockerfile, docker-compose.yml, fly.toml, vercel.json, netlify.toml), monorepo (turbo.json, nx.json, pnpm-workspace.yaml, lerna.json), API (route/endpoint patterns, openapi.yaml, swagger.json), data (*.ipynb, dbt_project.yml, airflow DAGs), docs (docs/ + mkdocs.yml/docusaurus.config.js/conf.py), production indicators (auth/session deps, .env.production, Docker).
Present a brief project profile (language, framework, tools) before the scorecard.
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.
- 8d ago First seen · 220 lines · 12 tokens per session scan B f9921f086946
setup is a skill published in the GitHub repository paulo-yamagishi/claude-code-setup (2 stars, last pushed 7mo ago), licensed MIT. It adds 12 tokens to every session and 3,342 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 2 findings (reads agent configuration directories, recursive force delete). It is 100% identical to setup, 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…