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 commands/koolamusic/claudefiles/setupgit clone --depth 1 https://github.com/koolamusic/claudefilesWhat 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.00024 | $0.02622 |
| Opus 5 | $0.00012 | $0.01311 |
| Sonnet 5 | $0.00005 | $0.00524 |
| Haiku 4.5 | $0.00002 | $0.00262 |
Grade B, and why
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 2d 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.
Users can enable later by hand: copy the relevant `settings:` fragment from `claudefiles.yaml` into their `~/.claude/settings.json` (or project-local `.claude/settings.json`), or set `"enabledPlugins": { "<plugin>": true How it starts
The opening of the file, as written. The whole thing — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Your task
Install claudefiles by reading the manifest and deploying everything to the target directory.
Step 1: Read the manifest
Read claudefiles.yaml in this repo root. It declares what gets installed and how.
Step 2: Ask install target
Ask the user:
- Global (recommended): Install to
~/.claude/— available in all Claude Code sessions - Local: Install to
./.claude/in the current project only
Step 3: Detect platform
Determine if running on macOS or Linux to resolve the {{sound_player}} template variable:
- macOS →
afplay - Linux →
aplay
uname -s
Step 4: Create target directories
mkdir -p <target>/skills
mkdir -p <target>/commands
mkdir -p <target>/sounds
mkdir -p <target>/hooks
Step 5: Copy files
Copy the contents declared in install.targets:
# Skills — copy each skill directory
cp -R skills/* <target>/skills/
# Commands — copy all .md files
cp commands/*.md <target>/commands/
# Sounds — copy all files
cp sounds/* <target>/sounds/
# Hooks — copy all hook scripts and make executable
cp hooks/* <target>/hooks/
chmod +x <target>/hooks/*
Step 6: Deploy nvim plugin overlays (skip per-file if exists)
Overlay dotfiles/nvim/lua/plugins/ onto ~/.config/nvim/lua/plugins/. The nvim_plugins target in the manifest has skip_if_exists: true at the file level — never overwrite an existing plugin file the user already customized.
mkdir -p ~/.config/nvim/lua/plugins
for src in dotfiles/nvim/lua/plugins/*; do
name=$(basename "$src")
dest="$HOME/.config/nvim/lua/plugins/$name"
if [ -e "$dest" ]; then
echo "nvim plugin $name already exists — skipping"
else
cp "$src" "$dest"
echo "nvim plugin $name installed"
fi
done
Record per-file outcomes for the summary.
Step 7: Smart-merge global CLAUDE.md
Deploy the global agent directives to <target>/CLAUDE.md using a smart-merge strategy:
- Read
dotfiles/CLAUDE.mdfrom this repo (the source directives) - If
<target>/CLAUDE.mdalready exists and is non-empty: a. Back it up:cp <target>/CLAUDE.md <target>/CLAUDE.md.backupb. Read the existing CLAUDE.md c. Smart-merge: Compare by section header (## headings). For each section in the source:- If the section doesn't exist in the target → append it
- If the section exists in the target → keep the target's version (user customizations win) d. Preserve any sections in the target that don't exist in the source (user's custom sections)
- If
<target>/CLAUDE.mddoesn't exist or is empty, copy the source as-is
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.
- 2d ago First seen · 207 lines · 24 tokens per session scan B f69e445bf62e
setup is a command published in the GitHub repository koolamusic/claudefiles (132 stars, last pushed 3d ago), licensed MIT. It adds 24 tokens to every session and 2,622 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.