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/remeic/ccm/claude-mdgit clone --depth 1 https://github.com/Remeic/ccmWhat 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.00777 | $0.00777 |
| Opus 5 | $0.00388 | $0.00388 |
| Sonnet 5 | $0.00155 | $0.00155 |
| Haiku 4.5 | $0.00078 | $0.00078 |
Grade A, and why
ccm 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 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.
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
Guidance for AI agents (and humans) working in this repo. See ARCHITECTURE.md for the design
deep-dive.
What this is
ccm (@remeic/ccm) — nvm-like manager for Claude Code profiles. Each profile is an isolated
CLAUDE_CONFIG_DIR, so multiple Claude accounts can coexist without re-login. CLI built on
commander + zod. Zero other runtime deps — keep it that way.
Commands
Bun is the dev package manager (bun.lock). Node 24 (.nvmrc, engines).
bun install
bun run build # tsup → single ESM file in dist/
bun run dev # tsup watch
bun run test # vitest
bun run test:coverage # vitest + coverage (gate)
bun run test:mutation # stryker (gate)
bun run lint # biome check
bun run lint:fix # biome check --write
bun run format # biome format
Non-negotiable invariants
- 100% coverage (vitest, all of branches/functions/lines/statements) and 100% mutation
(Stryker,
break: 100). Any new code must be fully tested AND mutation-proof. CI enforces both. - Every new
src/lib/*.tsand mutatedsrc/commands/*.tsmust be added tostryker.config.mjsmutate[]. Omitting it silently weakens the 100%-mutation claim — a reviewer will diffmutate[]againstsrc/. Add a directtests/lib/*.test.tsfor each new lib file; don't rely on caller coverage to kill mutants. src/index.tsandsrc/types.tsare excluded from coverage — keep them logic-free (registration and schemas only). Don't move testable logic there to dodge the gate.
Conventions
- ESM
.jsimport specifiers in.tssource (e.g.import { x } from './foo.js') — required by the bundler's module resolution. New files follow this. - Layering:
src/lib/*= pure, testable logic (named exports +/** JSDoc */).src/commands/*= CLI wiring (commander registration, I/O). Keep UI out of logic. - UI/output: colors, icons, and print helpers live in
src/lib/ui.ts(built onnode:utilstyleText, NO_COLOR/non-TTY aware). Never hand-write\x1b[...escapes in commands. - Errors:
formatErrorinsrc/lib/errors.ts; CLI error handling viarunActioninsrc/lib/run-action.ts(prints✗ message+exit(1)). Don't re-add per-command try/catch boilerplate; keep only inner try/catch that carries real rollback semantics. - Dependency-injectable seams: lib functions take
configFile/profilesDir/browsersDirparams defaulting to the real paths. This is what makes 100% coverage achievable — preserve the pattern. - Validation: all external input via zod schemas in
src/types.ts(profile names, config shape, Claude auth status). Parse with.safeParseand degrade gracefully. - Biome style: single quotes, no semicolons, trailing commas, 100-col width. Conventional Commits (commitlint-enforced).
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 · 56 lines · 777 tokens per session scan A 2c9d467a9ea3
ccm CLAUDE.md is an instructions file published in the GitHub repository Remeic/ccm (9 stars, last pushed 13d ago), licensed MIT. It adds 777 tokens to every session, about $0.0039 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-31.
Other instructions, from other repositories
shakespeare-writing-studio AGENTS.md
Instructions for ZCZHAO-1999/shakespeare-writing-studio, covering agent entry point, primary skill, what this agent should do, required reading order and hard rules.
woke_novel CLAUDE.md
Instructions for keyboardgdy/woke_novel, covering claude.md, 项目定位, 三层架构, 关键不变量 and 流水线与会话分组.
github-router AGENTS.md
Instructions for animeshkundu/github-router, covering github-router, build, lint, and test commands and code style guidelines.
github-router CLAUDE.md
Instructions for animeshkundu/github-router, covering github-router, primary deployment target, design docs, commands and test lanes (why bun run test is not bun test).
claude-code-webui CLAUDE.md
Instructions for sugyan/claude-code-webui, covering claude code web ui, code quality, setup for new contributors, install lefthook and install and verify hooks.
handoff CLAUDE.md
Claude Code instructions for dazuiba/handoff, covering claude.md, what handoff is, file map and how to release.