← ClaudeAtlas

reportlisted

Show how many tokens the Claude Code subscription spent, by project folder, session, day or model, with the API-equivalent cost. Use when the user asks where their tokens or usage went, what a project or a session cost, or for a usage report.
wachawo/quotaledger · ★ 0 · Data & Documents · score 73
Install: claude install-skill wachawo/quotaledger
# Usage report Run these two commands with the Bash tool, in this order: ```bash quotaledger ingest --quiet ``` ```bash quotaledger report $ARGUMENTS ``` The first brings the ledger up to date, the second prints the table. When the user gave no options, pick them from what they asked: `--by session` for sessions, `--project TEXT` for one project, `--since` and `--until` for a period (local days, inclusive), `--week previous` for last week, `--all` for the whole history. With no hint at all, run it without options: projects over the current subscription week. The limit line gives the last real reading with its time and, after "about", an estimate for now; keep the two apart when you summarise. `SHARE` is the part of the period a row accounts for, `LIMIT` the part of the weekly subscription limit it used; `LIMIT` is an estimate. Show the table exactly as printed, in a code block, then add at most two sentences on what stands out. Do not recompute or round the figures. When the user asks about the subscription limits or how much of the 5 hour or 7 day window a project used, run `quotaledger limits` instead of the report and show its output the same way. Its split by project is an estimate, say so. Add `--usd` only when the user asks about cost or money. Its `API USD` column is what the same usage would cost at the list prices of the API; a subscription is not billed per token, so present it as an equivalent, not as money spent.