cost-tracking
Track and report Claude Code token usage, spending, and budgets from the local ECC cost-tracker metrics log. Use when the user asks about costs, spending, usage, tokens, budgets, or cost breakdowns by model, session, or date.
Install
git clone https://github.com/affaan-m/ECC /tmp/ECC && ln -s /tmp/ECC/skills/cost-tracking ~/.claude/skills/cost-trackingFrom README
Cost Tracking Use this skill to analyze Claude Code cost and history from the metrics log that ECC's stop:cost-tracker hook writes. Where the data lives The tracker appends one JSON object per session-stop to /.claude/metrics/costs.jsonl. Each row is a cumulative snapshot for that session, so to total spend you take the latest row per sessionid and sum across sessions — summing every row multiply-counts. ECC also maintains internal per-session files under /.claude/metrics/cost-snapshots/ so runtime hooks can read the current session total without rescanning all history. Treat those files as a rebuildable cache; each snapshot stores a byte cursor so only newly appended rows are scanned. Stable reads are O(1), while updates are O(new bytes). Stale entries are pruned after 30 days or when the directory exceeds 512 sessions. Cold catch-up work is limited to 16 MiB per hook invocation, and malformed unterminated rows larger than 1 MiB are discarded with a resumable cursor.
More from this repo
api-design
REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning,...
article-writing
Used to write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive...
brand-voice
Used to build a source-derived writing style profile from real posts, essays, launch notes, docs, or site copy, then...