What problem does it solve? Agent harnesses (AGENTS.md, rules files, skills, and referenced docs) accumulate broken path citations, redundant instructions, and theory-heavy content that wastes context tokens without changing agent behavior. This Skill evaluates a repository's harness across three tracks and produces report-only findings without auto-editing anything. ## Core Features & Use Cases - Track A — Correctness: Deterministic script checks that cited paths and commands actually exist, preferring false negatives over false BROKEN flags. - Track B — Redundancy: Dual blind LLM judges with planted calibration traps classify claims as Ship/Review/Hold based on rediscovery cost. - Track C — Usefulness: Dual judges plus a fan-in gate classify surfaces as Slim/Keep-core/Mixed/Hold, emitting a mechanical KEEP/CUT apply plan for Mixed surfaces. - Use Case: Run a full harness eval on a repo to find dead links in AGENTS.md, trim instructions an agent would rediscover anyway, and identify skill files that are mostly theory before approving any edits. ## Quick Start Ask the agent to run a harness eval on this repository, then answer the Q1 optional-docs and Q2 track-budget questionnaires to choose the evaluation scope.