Claude Usage Analyst
Analyze Claude Code token usage, cost, quota burn, model mix, and cache read/write using ccusage evidence — and explain in human terms why your quota got exhausted.
Your Claude quota vanished and you have no idea which model or session burned it. This playbook reads the ccusage data and explains exactly where the tokens went.
Who it's for: Claude Code users, developers, teams managing AI spend
Example
"Why did my Claude quota run out today?" → A breakdown of tokens, cost, and model mix per session, pinpointing what burned the quota
CLAUDE.md Template
New here? 3-minute setup guide → | Already set up? Copy the template below.
npx ccplaybooks add claude-usage-analyst# Claude Usage Analyst
## Overview
Use this skill to produce evidence-based usage explanations from local `ccusage` data. Separate observed numbers from interpretation, and explain quota burn in human terms.
## Workflow
1. Verify `ccusage` is available:
```bash
ccusage --version
```Get new playbooks like this one
One email a week with new Claude Code workflows. Free, like everything here.
No spam. Unsubscribe anytime.
What This Does
Analyze Claude Code token usage, cost, quota burn, model mix, and cache read/write using ccusage evidence — and explain in human terms why your quota got exhausted.
What's Inside
The template covers:
- Workflow
- Evidence Rules
- Output Shape
Quick Start
Step 1: Create a Project Folder
Make a dedicated folder for this workflow and open it in Claude Code.
Step 2: Download the Template
Click Download above to save the template, then drop it into your project as CLAUDE.md (or paste it into your existing one).
Step 3: Start Working
Tell Claude what you need in plain language — it will follow the template's workflow automatically. For example:
Why did my Claude quota run out today?
Claude reads the template and runs the steps for you.