Usage Audit

Bloated context costs twice: you burn usage limits faster and output quality drops because models attend most to the start and end of context. This skill finds the waste and tells you what to cut.

Credit: adapted from the context-audit skill in the Claude Code Context Cleanup Guide (2026). Armory port adds package-aware checks and treats the scoring rubric as an overridable reference, not a verdict.

Step 1: Get /context Data

Check the conversation for recent /context output. If the user has not run it in this session, ask:

"Run /context in this terminal and paste the output. I can't run slash commands myself — once I can see the breakdown I'll audit everything it flags."