ai-usage-audit
manual$29

manual audit · $29 · 48h turnaround

Stop burning
tokens.

Hitting Claude Code limits before you should — on the $20, $100, or $200 plan? Find what's actually eating them, and fix it.

Get your audit for $29 one-time · no subscription
Not ready? Run the free script first →
usage report · last 14 days
$ npx ai-usage-audit --days 14
SESSION
LENGTH
TOKENS
marathon session (continued from summary)
6 days
128M
feature work
1 day
12.6M
refactor
4h
9.1M
bug hunt
3h
7.9M
+10 more sessions
78M
TOTAL236M tokens
236M
tokens in 14 days
128M
one marathon session · 54% of everything

// my own last 14 days: 236M tokens. one marathon session ate 128M.

how it works

Three steps. Your data stays on your machine.

  1. 01

    Pay $29

    One-time. No account, no subscription.

  2. 02

    Run my open-source script locally

    It's read-only. You send me only the JSON summary it prints. Raw logs never leave your machine. inspect the code on GitHub

  3. 03

    Get a personal report within 48h

    Top leaks, 3 concrete fixes, and how much limit you'd get back. Written by me, not a dashboard.

what you get

A breakdown, not a dashboard.

  • Session-by-session breakdown

    Which sessions blew up, and why the big ones got big.

  • Model usage check

    Burning Opus where a cheaper model would do just as well?

  • Cache analysis

    Whether you're re-sending context you should be caching.

  • Concrete workflow fixes

    Specific changes to how you work. Not "use fewer tokens".

For $29 I manually analyze your Claude Code usage report and send you a breakdown: where tokens leak and what exactly to change to stop hitting limits.

A real example — my own audit

AI Usage Audit — report

Period: last 14 days · Total: 236M tokens

The headline: one session is your entire problem.

Your top session burned 128M tokens — 54% of everything you used in two weeks. It was a marathon, continued from a summary. That restart helped once, then the session grew right back past 100M. This single session, not your daily work, is what pushes you into the limit.

Why it happened (and why it's not your prompts).

Your actual typed input over 14 days was ~75K tokens. That's 0.03% of the total. The other 99.97% is the model re-reading its own context on every message. You are not "using too much" — one long session is dragging its whole history behind it, and you pay to re-read it every turn.

Your cache is fine — ignore anyone who says otherwise.

Cache hit ratio: 99.97%. Caching is working perfectly. Your leak is NOT a caching problem. Advice like "improve your caching" is wrong for your usage. Your leak is 100% session length.

The 3 fixes, in order of impact:

  1. 1.

    Close sessions at task boundaries (biggest win). Compacting won't save you — it empties the trailer but the session refills it. What cuts usage is closing the session. When a task ends, start fresh. Need continuity? Paste a short summary into a new session instead of continuing the giant one. If that 128M session had been capped around 30M and split, you'd have avoided ~90M tokens — roughly 38% of your entire two-week usage.

  2. 2.

    Route simple work off Opus. 46% of your tokens ran on Opus. Refactors, boilerplate, and simple edits would look identical on a cheaper model. Keep Opus for genuinely hard reasoning, send the rest down. Even moving a third of that off Opus frees ~15M tokens of headroom.

  3. 3.

    Stop treating long sessions as productive. They feel efficient but eat your limit like a second subscription. Your output was 0.4% of everything — you're not paying for what Claude writes, you're paying for what it re-reads. Shorter, scoped sessions are the whole game.

Bottom line.

Between session hygiene and model routing, cutting 30-45% of your usage is realistic. On the $100 plan that means you stop hitting the weekly wall — without paying $200.

Artem

Who's doing your audit

I'm Artem, a freelance dev. I burned 236M Claude Code tokens in two weeks before I built the tool to see where they went. Now I go through yours by hand and write up what I find.

AI Usage Audit, manual reviewqty 1

Can't find real limit savings in your usage? Full refund, no questions.

one-time · no subscription · report within 48h · your data never leaves your machine
Can't find real limit savings in your usage? Full refund, no questions.

Want the automated tool instead?

I'm building it. Drop your email and I'll ping you at launch.