Sitemap

ccmd is built by Matthew Diakonov, the indie engineer behind claude-meter, skillhu.bz, and prompt-db. ccmd is the analyzer-plus-recommender wedge missing from the Claude Code tooling space.

README.md is human documentation, read once during onboarding, never enters Claude

Common questions about ccmd: how the in-browser analyzer works, polyglot support for AGENTS.md and .cursorrules and .grokrules, privacy, the Karpathy 12-rule rubric, and what changes after June 15 2026 Agent SDK billing split.

How ccmd scores an agent-config file: instant in-browser token math, the Karpathy 4-rule scorecard, per-line structural lints, and an Opus 4.7 rewrite that streams back as a marked-up diff with the dollar cost on every cut. Works on CLAUDE.md, AGENTS.md, .cursorrules, and .grokrules.

All 12 Karpathy rules for CLAUDE.md, each with the failure mode it catches, plus a paste-ready 24-line CLAUDE.md you can copy into your repo. Karpathy posted his Claude Code failure modes on X in Jan 2026; the community extended the original four to twelve. ccmd scores every paste against all 12.

ccmd privacy policy: what gets stored when you upload a file to the free analyzer, how to delete it.

Every page on ccmd, grouped by section.

The popular fix for a rule Claude keeps skipping is to delete it. That is backwards for most of them. ccmd

AGENTS.md picked plain markdown, a single root file, no required fields, no @-import, nested concatenation, and a 32 KiB cap. Each decision has a measurable consequence in tokens, cache behavior, or loader semantics. Here is each one, what it bought, and what it cost.

Your provider

Reddit threads use

A PreToolUse hook returning permissionDecision: \

A shared CLAUDE.md is not paid once. It is re-injected every turn of every session that loads it, so a team of M engineers working in parallel pays your per-turn token count M times simultaneously. The per-turn number ccmd prints is the per-seat floor; your headcount is the multiplier nobody puts on it. Here is the math, where the file gets re-paid, and how to attribute it per engineer.

An AGENTS.md token cost audit is four steps: paste, score, read three numbers, calibrate to your loader. Most audits stop at step three. The score itself is free (no signup, no upload, ~250ms in your browser). The dollar number you read off the screen is the upper bound for one specific path: Codex CLI, uncached, 30 turns, Opus 4.7 at $15 per million input tokens. Your actual bill is that number times your loader

AGENTS.md does not have one per-turn token cost. The same 640-byte file is 0 tokens per turn in Cursor, 0 in Claude Code without an @-import, the entire file in Claude Code with @AGENTS.md, the entire file in Codex CLI on uncached turns, and ~10% of the file on cached Codex turns. The number belongs to the host, not the file.

A Claude Code config is not a portable artifact. CLAUDE.md is a contract with seven specific anchor types in your project tree: file paths, scripts, .claude/settings.json hooks and MCP allowlist, @import targets, subdir CLAUDE.md, incident references, and stack lines. Copy it to another repo and each one breaks silently. Where each rule actually belongs, and what transfers vs. what doesn

Raw input grows as N(N+1)/2 across N turns, not linearly. At 200 turns that

Every CLAUDE.md audit on the internet measures tokens cut. An accuracy gain audit measures accuracy bought. It converts ccmd

Every CLAUDE.md guide quotes the file-level ceiling. The threshold that actually predicts ignored rules is per instruction, not per file. The ccmd analyzer fires at wordCount > 28, roughly 37 tokens per line, and credits back 35% of the line

Anthropic

CLAUDE.md is the only piece of config in your stack that fails silently. TypeScript yells, ESLint yells, CI yells. CLAUDE.md ships every byte to Claude on every turn and then says nothing when half the rules get ignored. The audit is 7 deterministic checks against the bytes you wrote, each one a finding kind at a known line in src/lib/analyzer.ts.

A starter template

Type /model in Claude Code and the file on disk does not change. The bill it produces, the rules it is allowed to enforce, and the cache it lives in all do. Most analyzers normalize cost to Opus, including ours, so the number you stare at is one specific model

Every custom subagent loads your full CLAUDE.md hierarchy at startup as a fresh read, and there

A Claude memory audit walks two files in order: CLAUDE.md (the one you wrote, ships every byte every turn) and MEMORY.md (the one Claude wrote about you, first 200 lines load every turn). Here are the seven CLAUDE.md finding kinds the analyzer checks, the one MEMORY.md check the analyzer does not yet ship, and the order to run them in under ten minutes.

We ran ccmd

If your CLAUDE.md is one line that reads @AGENTS.md, you are not looking at what Claude sees. Anthropic

AGENTS.md is positioned as a portable spec across coding agents. The spec is intentionally one paragraph. Every host then fills in the gaps differently. Same file on disk, four different in-context payloads.

Auto memory is the cousin of CLAUDE.md every audit forgets. MEMORY.md fires on every turn but only the first 200 lines load; the rest sit on disk invisible to Claude. On a real long-lived index of 1,135 lines, only 21,677 chars (~5,400 tokens) bill per turn. Here is what that looks like on disk, what the truncation does, and how to think about the per-file follow-read cost.

A Claude Code config audit is a line-by-line score of your CLAUDE.md (or AGENTS.md, .cursorrules, .grokrules) against the Karpathy 12-rule rubric, plus seven per-line finding kinds (bloat, vague, aspirational, conflict, duplicate, missing_why, cache_bust). The rubric is what makes it an audit instead of advice.

Switching Opus to Haiku caps the bill at 5x cheaper. A bloated CLAUDE.md moves it 4-10x. One cache-busting line in your config flips you from $0.50/M to $5/M at the same model, a 10x swing the model-pricing table never shows. The dial is context.

Every byte of CLAUDE.md re-uploads on every turn and feeds time-to-first-token. One date in the first 20 lines forces every session to pay the uncached TTFT instead of a cached-read TTFT. The two analyzer findings that double as latency findings, and the fixes.

Anthropic

There is no inline conditional rule syntax in CLAUDE.md. Every line is concatenated into the system prompt at session start and fires on every turn. The five

Fan out N parallel agents in Claude Code and your CLAUDE.md cost usually multiplies by N. Anthropic

A solo founder

An owner audit pairs git blame CLAUDE.md (who added each line, when) with a deterministic line-level analyzer. ccmd flags the three fingerprints stale lines leave behind: a stale timestamp, a duplicate rule, and a prohibition with no recorded reason. A repo grep and git blame name what is gone and who to ask.

Your CLAUDE.md is re-sent in full on every turn, so its per-turn token cost equals its whole token count. This is a flat number you can read off a table: characters / 4 = tokens, tokens x rate = dollars. Per-turn and per-session cost by file size at Opus 4.7, Sonnet 4.6, and Haiku 4.5 rates, plus the chars/4 vs new-tokenizer gap.

Every byte of CLAUDE.md is in the system prompt on every turn. Seven categories of those bytes produce zero behavioral signal. Our analyzer enumerates them as the Finding.kind union at src/lib/analyzer.ts:6. Per-category waste math, ranked by dollar impact, on Opus 4.7 at the rate the analyzer hardcodes.

If your repo has CLAUDE.md, AGENTS.md, and .cursorrules side by side, they have already drifted. The trick is that drift is measurable: the same Karpathy 12-rule rubric runs against all four formats, so a 7/12 CLAUDE.md next to a 3/12 .cursorrules is a literal 4-rule delta. The missing rules in the gap are where Claude and Cursor silently behave differently.

Per-turn token math hides what your CLAUDE.md actually costs you. The bill that throttles you is weekly. One 6,000-token file × five sessions × five days × thirty turns is 4.5 million input tokens before Claude has read a single line of your code. One ISO date on row 3 multiplies that by ten. The walkthrough, with the line of the analyzer that catches it.

Every line of CLAUDE.md is concatenated into the system prompt and re-sent on every turn. Our analyzer hardcodes that as estimatedTokensFireEveryTurn = totalTokens. But CLAUDE.md is one of four firing surfaces, and the other three (skills, hooks, MCP tool descriptions) fire conditionally. A walkthrough of which surface each kind of rule belongs on.

An analyzer scores one pasted CLAUDE.md. Claude Code concatenates a stack at launch: managed policy, ~/.claude/CLAUDE.md, the project file, and every @import it pulls. Worked on ccmd

A nested CLAUDE.md costs zero tokens at launch, the full file the moment Claude reads anything in its subtree, then zero again after /compact. The four token states of a subdirectory file, and why other guides stop at the first one.

Paste a .grokrules or .grok/GROK.md file and get a per-line score: Karpathy 12-rule pass rate, bloat, vague terms, missing-why prohibitions, cache-busting timestamps. Same rubric ccmd runs on CLAUDE.md, because Grok Build copied the format.

Most guides say

Long-form guides on the agent-configuration files that ship into your context on every turn. Token cost math, Karpathy-rubric scoring, rule-firing audits, AGENTS.md / .cursorrules / .grokrules comparisons, drift across models. Grouped by topic.

ccmd terms of service.