harness-auditlisted

Audits a Claude Code setup end-to-end: what loads every session, what it costs, and whether the harness's own claims hold. Inventories the standing surfaces (CLAUDE.md chain, personal/project/plugin skills, MCP instruction blocks, agent rosters, hooks, settings at every scope), quantifies their per-session token cost, runs five checks (self-consistency, duplication across scopes, enforcement parity, scope discipline, and a provisional routing-effectiveness check for doc-fleet repos) and reads the CLAUDE.md chain as intent (code outranks the doc; no restated stack, deps, or layout). Output is a quantified triage that stays in-repo: findings at machine scope (anything under ~/.claude, user or enterprise settings, global plugins) are reported for the owner to action, never edited. Use to review, slim, or sanity-check a whole Claude Code setup (including 'why is my context so big' or 'what loads every session') after major harness changes (a new plugin fleet, a new machine, a model release) or when sessions feel
claudialnathan/agent-kitchen · ★ 3 · AI & Automation · score 64

Install: claude install-skill claudialnathan/agent-kitchen

## The attention this skill redirects From "read the config files and comment" to "measure what every session pays before any work starts, then check the harness's claims against its own behavior." The default failure is a vibes review: opening CLAUDE.md, calling it well-written, and missing that the setup burns five figures of tokens per session on descriptions, instructions, and rosters nobody chose deliberately. The second failure is trusting the harness's documentation of itself: files that say "this is not loaded" while being loaded, checklists that say "always run X" with nothing enforcing X. The third failure is this skill's own trap: treating cost as the verdict. Tokens are what's easy to count; what a surface lets the owner produce is what decides, and an audit that only counts always lands on cut, because the cheapest harness is the empty one. A surface the owner reaches for is already earning its cost, and that she uses it is the evidence it clears the bar, not a number to override. Report what each surface costs so the owner spends deliberately; never strip toward zero. ## Step 1: Inventory the standing surfaces List everything that enters context at session start, with its scope and owner: - **Instruction files**: CLAUDE.md chain (enterprise → user `~/.claude/CLAUDE.md` → project → CLAUDE.local.md), auto-memory `MEMORY.md`. - **Skills**: personal (`~/.claude/skills/`), project (