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 instructions/koolamusic/claudefiles/claude-mdgit clone --depth 1 https://github.com/koolamusic/claudefilesWrote 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/instructions/koolamusic/claudefiles/claude-md)<a href="https://agentmods.dev/instructions/koolamusic/claudefiles/claude-md"><img src="https://agentmods.dev/badge/instructions/koolamusic/claudefiles/claude-md.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.00725 | $0.00725 |
| Opus 5 | $0.00362 | $0.00362 |
| Sonnet 5 | $0.00145 | $0.00145 |
| Haiku 4.5 | $0.00072 | $0.00072 |
Grade A, and why
claudefiles CLAUDE.md scanned grade A with 0 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 6d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This is a Claude Code configuration repository. It is opinionated toward Claude Code and does not target other AI coding assistants.
What this repo is
Portable configuration for Claude Code — skills, commands, hooks, sounds, and settings deployed to ~/.claude/. Think dotfiles, but for Claude.
Architecture
claudefiles.yaml is the source of truth. It declares install targets, settings to merge, and platform-specific values. The /setup command reads this manifest and does the deployment. No imperative installer scripts beyond bootstrap.
Setup command
/setup is a project-level command (.claude/commands/setup.md). It only works when Claude is running inside this repo. This solves the bootstrap chicken-and-egg: the command is available immediately after cloning, before anything is deployed globally.
Install targets
| Target | Directory | Deployed to |
|---|---|---|
| skills | skills/ |
~/.claude/skills/ |
| commands | commands/ |
~/.claude/commands/ |
| sounds | sounds/ |
~/.claude/sounds/ |
| hooks | hooks/ |
~/.claude/hooks/ |
| claude_md | dotfiles/CLAUDE.md |
~/.claude/CLAUDE.md (smart-merged) |
| nvim | dotfiles/nvim/ |
~/.config/nvim/ |
| plugins | plugins/ |
Installed by Claude Code via marketplace |
Note: commands/ contains only global commands (/gitcommit, /gitconfig). /setup lives in .claude/commands/ as a project-level command and is not deployed globally.
Plugins
This repo is a registered Claude Code plugin marketplace (koolamusic/claudefiles). Plugins in plugins/ are discovered via .claude-plugin/marketplace.json and installed as <name>@claudefiles. Setup merges extraKnownMarketplaces and enabledPlugins into settings.json — Claude Code handles the actual plugin installation on next startup.
Git configuration (dotfiles/) is installed separately via /gitconfig.
Settings merge
settings.json is a reference file showing the final structure. The manifest's settings section uses template variables ({{sound_player}}) resolved at install time based on platform detection.
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.
- 6d ago First seen · 56 lines · 725 tokens per session scan A 747a60c7d243
claudefiles CLAUDE.md is an instructions file published in the GitHub repository koolamusic/claudefiles (132 stars, last pushed 7d ago), licensed MIT. It adds 725 tokens to every session, about $0.0036 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.