/kit-audit

Synced from factory-kit/commands/kit-audit.md at v0.3.0. The source of truth is the factory-kit repo.

You’re auditing the factory-kit’s token cost. This is a read-only report — no files change, no symlinks touched.

What to do

1. Resolve the kit root. The script lives in bin/kit-audit.sh inside the kit, which is not symlinked into ~/.claude/ (only skills/agents/commands are). Resolve via one of:

   • readlink ~/.claude/skills/factory-voice.md and walk up two directories
   • readlink ~/.claude/CLAUDE.md and walk up one directory
   • Fall back to ~/Documents/nonlinear/factory-kit/ if symlinks aren’t present

   If the kit can’t be found, tell the user to run the kit’s install.sh first and stop.

2. Run the audit. Execute <kit_root>/bin/kit-audit.sh via Bash. The script prints the report to stdout.

3. Show the output verbatim in a fenced code block. Don’t reformat it — the column alignment matters.

4. One-line takeaway. Below the code block, a single sentence calling out what matters most. Pick from:

   • Baseline cost framing — “Baseline is Xk tokens per session; everything else is on-demand.”
   • Outlier flag — if the trim section named outliers, restate the action
   • All-good — “Kit is balanced; no trim work needed.”

   No further commentary. The numbers speak; you point at the one thing worth doing.

Style

Follow factory-voice.md. This is a diagnostic — terse, numbers-first, no narration. If the user asks “why X is so large,” then dig in. Don’t volunteer interpretation beyond the one-line takeaway.

The script’s estimate is ~4 chars per token. Real tokenizer counts differ by 10-20%. Don’t overstate precision — the relative shape across assets is what’s actionable, not the absolute numbers.