Skip to main content

UsageSniffer

PyPI CI License: MIT

Scan your local Claude Code, Codex, Opencode, Gemini CLI, Copilot CLI, Cursor, Aider, and Continue sessions and see visually what eats your tokens — skills, thinking, tools, context cache, plus dollar costs, anomalies, and cross-agent comparisons.

Zero-dependency Python. Your session logs never leave the machine.

Install

Requires Python 3.10+.

Windows (PowerShell):

winget install Python.Python.3.12
pip install usagesniffer        # or: pipx install usagesniffer
usagesniffer scan --top 10

macOS:

brew install python pipx
pipx install usagesniffer
usagesniffer scan --top 10

Linux:

pipx install usagesniffer        # or: pip install usagesniffer
usagesniffer scan --top 10

Or run from a checkout with no install: python3 -m usagesniffer scan --top 10.

OS notes

  • Windows: Claude (%USERPROFILE%\.claude), Codex (%USERPROFILE%\.codex), Opencode (%USERPROFILE%\.local\share\opencode\opencode.db), Gemini, Copilot, and Continue resolve automatically. Cursor is read from %APPDATA%\Cursor\User. If your stores live elsewhere: usagesniffer scan --opencode-db PATH --cursor-dir DIR --aider-path FILE (Opencode also honors the OPENCODE_DB env var).
  • macOS: Cursor is read from ~/Library/Application Support/Cursor/User; everything else is home-relative and just works.
  • Linux: default paths as listed in "What it reads" below.

Quick start

usagesniffer scan --top 10                     # everything
usagesniffer scan --agents claude --top 5
usagesniffer session 05062c81                  # drill into one session (prefix match)
usagesniffer cost --top 10                     # dollar rollup + cache savings
usagesniffer cost --budget 50                  # exit 2 + alert when over $50
usagesniffer report -o report.html
usagesniffer watch --interval 30               # live burn (Ctrl-C to stop)
usagesniffer anomalies                         # outlier sessions vs agent baseline
usagesniffer skills-roi                        # per-skill cost table
usagesniffer compare                           # cross-agent efficiency
usagesniffer doctor                            # proactive waste audit (read-only, with fixes)
# filters work on most commands:
usagesniffer scan --since 2026-09-01 --project Sunrise --model sonnet

What it reads

Agent Source Ground-truth token signal
Claude ~/.claude/projects/*/*.jsonl message.usage: input / output / cache_creation / cache_read per assistant message
Codex ~/.codex/sessions/**/*.jsonl event_msg → token_count: last_token_usage per step (input / cached / output / reasoning)
Opencode ~/.local/share/opencode/opencode.db message.data.tokens + part rows (text / reasoning / tool)
Gemini ~/.gemini/tmp/*/chats/*.json per-message tokens {input, output, cached, thoughts, tool}
Copilot ~/.copilot/session-store.db assistant_usage_events per turn (input / output / cache / reasoning). Subscription billing → $ unknown
Cursor ~/.config/Cursor/User/**/state.vscdb ⚠️ per-bubble tokens read as zero on current builds; char-estimated, cost from usageData.costInCents when present
Aider .aider.chat.history.md / --analytics-log JSONL real tokens only via analytics log (prompt_tokens, completion_tokens, cost); transcripts are char-estimated
Continue ~/.continue/sessions/*.json session usage {promptTokens, completionTokens, cachedTokens} when the model reports it

Attribution buckets

Real totals always come straight from the logs. The buckets are token-weighted estimates (labelled as such in output):

  • thinking — Claude thinking blocks / Codex reasoning_output_tokens / Opencode reasoning parts
  • skills — SKILL.md loads, skill-instruction blocks, Skill-tool calls
  • tools — tool_use + tool_result / exec payload share
  • context_cache / context_write — cache read / creation tokens
  • assistant_text, system, user, other

The second chart ("action share EXCLUDING context cache") is the useful one: cache reads dominate raw totals but are cheap; the action chart shows where your real budget goes.

Layout

usagesniffer/
  models.py            # SessionRecord / ScanResult
  analyze.py           # aggregation
  pricing.py           # per-model $/Mtok rates + cost rollups
  insights.py          # anomalies, skill ROI, cross-agent compare
  render.py            # terminal ASCII charts (stdlib only)
  report.py            # self-contained HTML report
  cli.py               # scan | top | session | cost | report | watch |
                       #   anomalies | skills-roi | compare
  parsers/
    claude.py codex.py opencode.py gemini.py
    copilot.py cursor.py aider.py continue_.py
tests/
  smoke_fixtures.py    # synthetic sessions through the real pipeline

Roadmap

  • per-model pricing + $ cost rollup (cost, --budget)
  • --watch live mode
  • static HTML report export (report)
  • prompt-caching savings estimate (cache_read vs full-price replay)
  • 8-agent coverage (Claude, Codex, Opencode, Gemini, Copilot, Cursor, Aider, Continue)
  • anomalies, skill ROI, cross-agent compare
  • proactive doctor audit (skill weight, output hogs, model fit, cache reuse, disk)
  • PyPI publish (pipx install usagesniffer)
  • Homebrew / AUR packages — templates in packaging.md

Metadata

Release files for usagesniffer 1.2.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for usagesniffer 1.2.0
File Size Uploaded Provenance Actions
usagesniffer-1.2.0.tar.gz 30.2 kB With provenance Details for usagesniffer-1.2.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for usagesniffer 1.2.0
File Interpreter ABI Platform Actions
usagesniffer-1.2.0-py3-none-any.whl Python 3 none any Details for usagesniffer-1.2.0-py3-none-any.whl

Total release size: 67.3 kB

Release files / usagesniffer-1.2.0.tar.gz

Download URL usagesniffer-1.2.0.tar.gz
Size 30.2 kB
Tags Source
SHA-256 checksum
How to use checksums
4a39cca0b09c558f3a4156f6e4fc1447db0093dd39009a2cbf8e19dc6ff0c6e7
BLAKE2b-256 checksum
How to use checksums
28f4ff8ae7bc74481e6ce42fb4f4857f24f222ae3dca1bcc5ffbb210ef142ed5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Sep 17, 2026.

Transparency log

Release files / usagesniffer-1.2.0-py3-none-any.whl

Download URL usagesniffer-1.2.0-py3-none-any.whl
Size 37.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
c061feacf431c95fb5628a8eba30e1c1ac216ca2dca3056b3e4a2dbeb479f5f6
BLAKE2b-256 checksum
How to use checksums
8aa9a0f65ef0f68bc523a5fac4471635a69bafbd2cfb6e838483d50659a2205f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Sep 17, 2026.

Transparency log

Security for usagesniffer 1.2.0

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.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for usagesniffer-1.2.0.tar.gz

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 Sep 17, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page