usage-report

What problem does it solve?

Claude Code users lack built-in visibility into their token consumption, model-specific spend, and five-hour billing block usage across projects and sessions, making it difficult to control costs, enforce model selection policies, and avoid unexpected usage overruns.

Core Features & Use Cases

• Multi-Mode Usage Reporting: Generate daily, weekly, monthly, session, or billing block summaries of token spend and estimated costs, grouped by project or model.
• Per-Agent Attribution: For teams using the agents-observe plugin, break down token usage by individual subagents, including delegation chains and model compliance checks.
• Billing Block Safeguards: Monitor active five-hour billing block consumption and burn rate to prevent overages, with integration for loop circuit breaker checks. Use case: A development team lead can use this skill to pull a weekly spend report to identify if expensive Opus models are being used for low-complexity read-only tasks, violating internal model selection policies.

Quick Start

Use the usage-report skill to generate a weekly summary of your Claude Code token spend and top projects by usage volume.