codeburn-claude-cost-dashboard — Claude Code skill: setup
Skill runs the CodeBurn terminal dashboard to inspect Claude Code token expenses. It analyzes local session files on disk without API keys or proxy setups.
npx skills add reason-machines/trending-skills --skill codeburn-claude-cost-dashboard -a claude-codeWhat codeburn-claude-cost-dashboard does
This tool brings a terminal interface for monitoring coding agent costs. CodeBurn parses JSONL logs stored inside ~/.claude/projects/ directly. It reads model names, token counts, and tool executions. To prevent inflated numbers across overlapping runs, it deduplicates entries using API message IDs.
Sessions get organized into 13 deterministic activity groups, including coding, debugging, planning, and testing. For file modifications, the dashboard tracks a one-shot rate that shows how often the model succeeded without retry cycles. Pricing details come from LiteLLM and stay cached for 24 hours in ~/.cache/codeburn/.
Running this tool requires Node.js 20 or newer alongside an active Claude Code setup. If ~/.claude/projects/ contains no session data, the dashboard cannot display any stats.
What it helps with
- inspect Claude Code token expenses across projects
- break down spending by model and activity category
- calculate one-shot success rates on code modifications
- export session metrics to JSON and CSV files
Example prompts for the agent
- Check my Claude Code spending for today
- Launch the CodeBurn dashboard to review model token costs
- Export my session usage report to JSON
How to install codeburn-claude-cost-dashboard
1Skills CLI (Vercel)
npx skills add reason-machines/trending-skills --skill codeburn-claude-cost-dashboard -a claude-code2Manually: put the files in place
~/.claude/skills/codeburn-claude-cost-dashboard/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/codeburn-claude-cost-dashboard/
1Skills CLI (Vercel)
npx skills add reason-machines/trending-skills --skill codeburn-claude-cost-dashboard -a codex2Manually: put the files in place
.agents/skills/codeburn-claude-cost-dashboard/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add reason-machines/trending-skills --skill codeburn-claude-cost-dashboard -a cursor2Manually: put the files in place
.cursor/skills/codeburn-claude-cost-dashboard/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install reason-machines/trending-skills codeburn-claude-cost-dashboard2Manually: put the files in place
.github/skills/codeburn-claude-cost-dashboard/SKILL.md1Skills CLI (Vercel)
npx skills add reason-machines/trending-skills --skill codeburn-claude-cost-dashboard -a gemini-cli2Platform CLI
gemini skills install https://github.com/reason-machines/trending-skills --path skills/codeburn-claude-cost-dashboardManually: put the files in place
.devin/skills/codeburn-claude-cost-dashboard/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add reason-machines/trending-skills --skill codeburn-claude-cost-dashboard -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about codeburn-claude-cost-dashboard
How do I install codeburn-claude-cost-dashboard in Claude Code?
Run npx skills add reason-machines/trending-skills --skill codeburn-claude-cost-dashboard -a claude-code.
What does codeburn-claude-cost-dashboard do?
It provides terminal dashboard commands to inspect Claude Code token usage, model fees, and task breakdowns from local logs.
Does CodeBurn require network API keys to track costs?
No, it works offline against local JSONL transcripts in ~/.claude/projects/ without third-party proxies.