What problem does it solve? Claude Code usage across chats, skills, subagents, and projects leaves no consolidated bill, making it impossible to answer questions like what a chat, branch, or pull request actually cost at API list prices. ## Core Features & Use Cases - Incremental cost collection: Scans session transcripts and appends priced records to an append-only ledger, with idempotent backfill and live pricing fetched from the official pricing page. - Flexible reporting: Aggregates the ledger by session, skill, project, model, day, component, git branch, or PR, with JSON output for post-processing. - Outcome-based cost analysis: Computes cost per merged PR or per completed build block, plus cache utilization ratios, so cross-model comparisons use per-outcome figures rather than misleading per-token numbers. - Use Case: After finishing a feature branch, ask what that PR cost; the skill resolves the branch via gh, reports its API-equivalent spend, and notes when multiple PRs share one branch's cost. ## Quick Start Ask the assistant to collect fresh cost data and report what this chat or this month's usage cost at API list prices.