What problem does it solve? AI coding-agent token spend is hard to trace back to the work it actually funded. This Skill answers questions about where Claude Code tokens went, what a story or epic cost, and how burn is pacing, using deterministic numbers from a local metered ledger instead of estimates. ## Core Features & Use Cases - Spend Queries: Break down token usage by story, epic, model, or week, with unattributed spend always shown rather than hidden. - Story Costing: Report total tokens, cache-read share, and tokens-per-point for a specific tracker key such as PLAT-482. - Burn Pacing: Relay pace data comparing spend against linear and work-weighted targets without extrapolation. - Attribution Inbox: Walk through unresolved attribution items one at a time and apply resolutions, pins, or repo defaults that re-meter sessions. - Use Case: Ask "what did PLAT-123 cost" and receive one line with total tokens, cache-read share, and tokens-per-point, all computed by the engine from local transcripts and git history. ## Quick Start Ask where your tokens went this week and the Skill will meter any new sessions, then report spend by account with unattributed share and open spend.