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/jerry0022/dotclaude/setup-projectnpx skills add Jerry0022/dotclaude --skill setup-projectgit clone --depth 1 https://github.com/Jerry0022/dotclaudeWhat 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.00097 | $0.02841 |
| Opus 5 | $0.00048 | $0.01421 |
| Sonnet 5 | $0.00019 | $0.00568 |
| Haiku 4.5 | $0.00010 | $0.00284 |
Grade A, and why
setup-project 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 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.
Asks the agent to reveal its instructionslowSystem prompt leakage
Directions to print, repeat or translate the system prompt extract configuration the operator did not intend to expose.
4. **`--fix` action**: print instructions to enable **Settings → Bypass permissions mode** in the Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 292 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup Project — Repo Hygiene
Audit or initialize a project's repository structure.
Step 0 — Load Extensions
Check for optional overrides. Use Glob to verify each path exists before reading. Do NOT call Read on files that may not exist — skip missing files silently (no output).
- Global:
~/.claude/skills/setup-project/SKILL.md+reference.md - Project:
{project}/.claude/skills/setup-project/SKILL.md+reference.md - Merge: project > global > plugin defaults
Arguments
--audit: Check existing repo and report issues (default for existing repos)--init: Full initialization — create missing files, set up ignores, scaffold extensions--fix: Auto-fix issues found during audit
No argument: detect if repo is new (no commits) → --init, otherwise → --audit.
Step 1 — Analyze the project
git status— is this a git repo?- Detect tech stack from manifest files (
package.json,Cargo.toml,pyproject.toml,go.mod,*.csproj) - Read existing
.gitignore - Check
LICENSE,README.md,.claude/directory - Detect monorepo structure (
packages/,apps/,workspaces)
Step 2 — .gitignore
2.1 — Language/Framework ignores (dynamic)
Instead of shipping static templates, fetch the appropriate rules:
- Detect the project's language/framework from Step 1
- Fetch from
gitignore.ioAPI:https://www.toptal.com/developers/gitignore/api/{stack}- Example:
node,python,rust,go,csharp,java
- Example:
- For IDEs, also fetch:
visualstudiocode,intellij,vim, etc. - Merge fetched rules with the mandatory sections below
If the API is unavailable, fall back to basic rules from Claude's knowledge.
2.2 — Claude / AI tooling ignores (mandatory, always included)
See deep-knowledge/claude-directory-structure.md for the canonical .claude/ layout.
MUST be tracked (never ignore):
CLAUDE.md,.claudeignore(root level, required by Claude Code).claude/commands/,.claude/skills/,.claude/hooks/.claude/settings.json,.claude/agents/,.claude/agents.json,.claude/launch.json.claude/graphify.json— the graph opt-out/consent record. It is a deliberate project decision, not runtime state, and ignoring it silently re-enables the graph for everyone who clones the repo..claude/deep-knowledge/,.claude/project-map.md— authored content.
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 · 292 lines · 97 tokens per session scan A 0d734fb6ea1d
setup-project is a skill published in the GitHub repository Jerry0022/dotclaude (4 stars, last pushed 3d ago), licensed MIT. It adds 97 tokens to every session and 2,841 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (asks the agent to reveal its instructions). 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…