auditlisted

## Purpose `/context` itemises skills, agents, and MCP tools natively. For those, run it and read the tables. What it structurally cannot itemise is the built-in tool pool: `System tools` and `System tools (deferred)` are lump sums, and together they are typically the largest single contributor to the fixed startup payload. This skill measures that attribution on the consumer's own machine by A/B differencing: a baseline session versus one session per candidate tool with that tool denied by bare name, which is compositional (deltas add), so a basket of trims can be priced from its members. Two rules govern everything this skill says, per the plugin's [`reference/engine.md`](reference/engine.md): 1. **Only measured numbers are reported.** No token figure, tool inventory, or threshold ships in this skill; values drift with every CLI release. If a number was not produced by a run on this machine in this audit, it is not stated. 2. **Every report is stamped** with the measured binary path and version, the measurement mode (`sdk` exact vs `cli-parse` display-rounded), and the session kind (headless). Machines with two CLI installs produce different answers per binary; the stamp is what makes the answer a claim instead of a guess. ## Scope boundary (route out) - Unused skills/plugins/MCP servers by usage history → the bundled `/doctor` (it is `disableModelInvocation: true`, so tell the operator to run it themselves; never reimplement its checks). - Per-skill