claude-cost
Live terminal dashboard for tracking Claude Code token usage and costs.
Install as a Claude Code skill
/plugin marketplace add mohsinahad/claudemeter
/plugin install claude-cost@claude-cost
Then use:
/claude-cost # launch live dashboard in a new tab
/claude-cost summary # print today/month costs inline
/claude-cost reset # reset config to defaults
Install as a standalone CLI
pipx install claude-cost # recommended
# or
pip install claude-cost
Note: If pip warns that the script is installed in
~/.local/binwhich is not on PATH, add this to your~/.zshrcor~/.bashrc:export PATH="$HOME/.local/bin:$PATH"
Then run:
claude-cost # live dashboard
claude-cost summary # quick inline summary
claude-cost reset # reset config
Budget alerts
Set spending limits in ~/.claude/dashboard_config.json:
{
"daily_budget": 5.00,
"monthly_budget": 50.00
}
To get automatic warnings after each Claude session, add a hook to ~/.claude/settings.json:
{
"hooks": {
"Stop": [
{
"hooks": [
{
"type": "command",
"command": "claude-cost check-budget"
}
]
}
]
}
}
Claude will print a warning in your session whenever you hit 80% or 100% of your budget.
Usage
claude-cost --help # show help
claude-cost --version # show version
claude-cost # launch the dashboard
claude-cost summary # print costs inline (no TUI)
claude-cost check-budget # check limits (exits 2 if over 80%)
claude-cost reset # reset config to defaults
Keys inside the dashboard:
| Key | Action |
|---|---|
q |
Quit |
r |
Refresh |
1 |
Last 24 hours |
7 |
Last 7 days |
3 |
Last 30 days |
What it shows
- Token usage (input / output / cached) per model
- Cost breakdown by session and cumulative
- Human cost estimate (time saved vs. manual coding)
- Live-updating as you work
No API key or extra config needed — reads directly from ~/.claude/.
Requirements
- Python 3.11+
- Claude Code installed and used at least once (data lives in
~/.claude/)
Metadata
Release files for claude-cost 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| claude_cost-0.2.0.tar.gz | 15.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| claude_cost-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 31.0 kB
Release files / claude_cost-0.2.0.tar.gz
| Download URL | claude_cost-0.2.0.tar.gz |
|---|---|
| Size | 15.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
08fc4538c3370d08fa14b7b38ced678385180bff61622ae76e7f4eca27a8ab4c
|
|
BLAKE2b-256 checksum How to use checksums |
88629b1976cad6750c969bfd8cf779a8e86a6de7766a6ff66578f57dd73ba1cd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 13, 2026.
Transparency logRelease files / claude_cost-0.2.0-py3-none-any.whl
| Download URL | claude_cost-0.2.0-py3-none-any.whl |
|---|---|
| Size | 15.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
365d142f078472548ea3d4c2b57c7f0e2c952778b8490e6f9bbc2f922ad7baed
|
|
BLAKE2b-256 checksum How to use checksums |
b23babd87e4934d954a0b9b76f476002e0cae4f4dad3c428cba069c410e1a8dc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 13, 2026.
Transparency log