2,009 Claude Sessions, 95 Million Tokens, and $15,345 of AI — Fully Itemized

Radical Transparency Series

2,009 Claude Sessions, 95 Million Tokens, and $15,345 of AI — Fully Itemized

I export my own AI usage every week and let a script tear it apart. Here is exactly where the money, the tokens, and the hours actually went — no rounding, no hiding.

All-time spend*
$15,345
API-equivalent estimate

Total sessions
2,009
~$7.64 each

Output tokens
95.5M
+30.4M in, 18.4B cached

Last 7 days
$1,110
163 sessions

*Every dollar figure here is an API-equivalent estimate at public list prices — a way to value the work, not a bill I actually paid. More on that in the methodology section.

We have one rule that never bends: you can’t improve what you don’t measure. We say it about ad spend, about content, about hiring. So it would be pretty hypocritical to pour thousands of dollars of AI into the business every month and have no idea where it goes.

So I instrumented it. Every Claude desktop session I run gets logged locally. Once a week a script reads every transcript, tallies the tokens by model, estimates the cost, and emails me a report. This article is that data, opened up for everyone.

If you’re an operator, a marketer, or a founder trying to figure out whether AI is a toy or a line item that deserves a budget, this is the honest picture of what heavy, daily use actually looks like.

New here? Start with our complete guide to how to use Claude, see how we use it to build marketing systems, meet the full agent roster, or watch a Claude agent build a website end to end.

📅 The last seven days

July 11–17, 2026 · 163 sessions · 7,122 assistant messages · 8.4M output tokens · ~$1,110.15

Here’s the week, day by day. Notice the shape — a quiet weekend, a steady climb, and then Thursday detonates.

Estimated cost per day (USD)

$3

$95

$182

$234

$28

$136

$432

Fri 11
Sat 12
Sun 13
Mon 14
Tue 15
Wed 16
Thu 17

The Thursday spike. On July 17 alone I ran 67 sessions and 2,799 assistant messages — about 39% of the entire week’s cost in a single day. That wasn’t me typing faster. It was scheduled automations firing (SEO monitors, a website-request intake job, a citation audit) plus a cluster of email-driven sessions. When you automate AI, your usage stops looking like a human’s calendar and starts looking like a server’s.

The weekday-vs-weekend gap is the other tell. Friday the 11th cost $3.48. Thursday cost $431.60 — a 124× difference inside one week. Averaged out, each session ran about $6.81, but averages hide everything interesting here.

🧮 The all-time picture

2,009 sessions · 30.4M input + 95.5M output tokens · 18.35B cache-read tokens · ~$15,345.18

Zoom out and the numbers get large fast. Across every session on record I’ve generated 95.5 million output tokens — roughly the equivalent of writing 70+ million words. Input was another 30.4 million tokens. And then there’s the number almost nobody talks about: 18.35 billion cache-read tokens.

Why caching is the hero

Cache-read tokens are billed at roughly a tenth of normal input tokens. Because agent sessions re-read the same context over and over, 18.35B tokens flowed through cache. Without prompt caching, this bill would be multiples higher. Caching is the single biggest reason heavy agent use is even affordable.

The per-unit math

$7.64 per session on average. About 47,500 output tokens generated per session. These aren’t quick chats — each session is a multi-step agent doing real work: browsing, coding, researching, writing files.

💸 Where the money goes: cost by model

One model eats more than half the budget.

This is the chart that changed how I think about model selection. A single model — Claude Opus 4.8 — accounts for 58% of all-time spend. The premium models (the Opus family) together are ~82% of the bill, while the fast, cheap models (Sonnet and Haiku) do a meaningful chunk of the work for pennies.

$15.3K
total

Claude Opus 4.8 · primary workhorse$8,85158%
Claude Fable 5$2,62717%
Claude Opus 4.6$1,73211%
Claude Opus 4.7$1,0187%
Claude Sonnet 5$9676%
Claude Sonnet 4.6$1140.7%
Claude Haiku 4.5$360.2%

The lesson operators miss: Haiku did over a million output tokens of work for $36. Opus is worth its premium for hard reasoning, but if you route every task to your most expensive model, you’re overpaying by an order of magnitude on the easy 60%. Match the model to the job — the way you’d never send your highest-paid strategist to alphabetize a spreadsheet.

🔥 The busiest days on record

June ran hotter than July. The current week doesn’t even crack the top 10.

Context matters. This week’s $1,110 feels big until you line it up against the real peaks. My single most expensive day ever — June 14 — cost more by itself (~$1,099) than this entire week did.

# Date Sessions Messages Est. cost
1 Jun 14 103 4,251 $1,099.17
2 Jun 27 55 2,446 $698.66
3 Jun 12 55 3,159 $655.71
4 Jul 3 56 2,638 $617.13
5 Jun 28 91 2,576 $607.07
6 Jun 24 35 1,871 $605.83
7 Jun 10 100 3,766 $550.77
8 Jun 26 13 1,652 $549.41
9 Jul 2 55 3,117 $533.36
10 Jul 4 73 3,841 $529.55

Interesting wrinkle: day #8 (June 26) hit $549 with only 13 sessions, while day #7 (June 10) needed 100 sessions to reach a similar number. Session count and cost are only loosely correlated — a handful of deep, long-running agent jobs can outspend a hundred quick ones.

🛠️ What the AI is actually doing

Tokens tell you the volume. Tool calls tell you the work.

The most revealing dataset isn’t tokens or dollars — it’s which tools the agent reaches for. This is the fingerprint of real operational work, not chatting. Here are the top eight, all-time:

Chrome · run JavaScript7,104
Chrome · control screen4,310
Shell · run bash (sandbox)3,514
Read a file2,054
Shell · run bash2,028
Chrome · navigate1,800
Write a file1,714
Web search1,660

Read that top line again: the single most-used tool is browser automation — running JavaScript inside Chrome, 7,104 times, plus 4,310 screen-control actions and 1,800 navigations. Add it up and browser control is by far the dominant activity. The AI isn’t just answering questions; it’s driving software — logging into dashboards, pulling reports, filling forms, checking rankings. These are the same AI agents we deploy for clients, each with a defined role in the agent roster.

Behind that: shell commands (5,500+ combined) for running code and data jobs, file reads and writes (3,700+) for producing deliverables, and 1,660 web searches for live research. This is the profile of a digital worker, not a chatbot.

⚙️ How the tracking actually works

The whole system is four moving parts and runs itself.

You don’t need enterprise tooling to measure your own AI use. My entire pipeline is a local script and a scheduled job. Here’s the flow:

🗂️
Session transcripts
Every desktop agent session is logged locally

🐍
Analyzer script
Python parses tokens, tallies by model, estimates cost

📊
Reports + dashboard
Plain-text, JSON, and a visual HTML dashboard

📧
Weekly email
Auto-sent every Monday, 8am, no hands

A scheduled job runs the analyzer every Monday at 8am. It regenerates the report, refreshes the dashboard, and an agent task emails me the summary an hour later. The only human step is reading it — and now, occasionally, publishing it.

Want to build your own? The recipe is simple: (1) find where your AI tool stores session logs, (2) write a script that sums tokens per model, (3) multiply by public per-token prices to get an API-equivalent estimate, (4) schedule it weekly. The measurement itself costs nothing and changes your behavior immediately. (We wire the same automations up for clients.)

🎯 Five takeaways you can steal

1
Measure before you optimize. I had no intuition for my own usage until I graphed it. The Thursday spike and the model concentration were both invisible to me until the data was in front of my face.

2
Route by difficulty, not by habit. One model is 58% of my spend. Some of that work could run on a model costing a fraction as much. Cheap models did over a million tokens of real output for tens of dollars.

3
Automation reshapes your cost curve. Scheduled jobs turned one Thursday into 39% of a week. That’s not a warning — it’s the point. But you have to see it to budget for it.

4
Caching is the affordability lever. 18.35 billion cache-read tokens is why this is viable. If your agent setup isn’t reusing cached context, you’re leaving the biggest savings on the table.

5
Value the output, not just the invoice. $15K of API-equivalent work is the real question: did it produce more than $15K of value? For me — websites shipped, reports generated, rankings monitored, hours reclaimed — that’s an easy yes. Track the numerator too.

📌 Methodology & honest caveats

These are estimates, not a bill. Every dollar figure is an API-equivalent value computed at public list prices. Subscription plans don’t charge per token, so this is a way to value the work — not what hit a card.

Scope. The data covers my Claude desktop/agent sessions logged locally, plus any command-line agent logs. It does not include claude.ai web or mobile chats, which aren’t stored on my machine — so real total usage is higher than what’s shown.

Freshness. Figures are drawn from my automated report generated the week of July 17, 2026. Token counts are rounded for readability (e.g., “8.4M”); percentages are computed from the underlying cost figures.

The bottom line

AI stopped being a novelty in our business the moment it became a measurable line item. $15,345 of API-equivalent work across 2,009 sessions isn’t a story about spending — it’s a story about leverage you can audit.

The tools you use every day are throwing off data. Capture it, chart it, and you’ll make better decisions in a week than you would guessing for a year. That’s true for your ad accounts, your funnels, and now your AI.

Measure everything. Then measure the measuring.
If you’re figuring out how to bring AI into your business the right way, that’s exactly what we teach in the AI Builder program — start with the numbers, build the system, then scale it.

Dennis Yu
Dennis Yu
Dennis Yu is the CEO of Local Service Spotlight, a platform that amplifies the reputations of contractors and local service businesses using the Content Factory process. He is a former search engine engineer who has spent a billion dollars on Google and Facebook ads for Nike, Quiznos, Ashley Furniture, Red Bull, State Farm, and other brands. Dennis has achieved 25% of his goal of creating a million digital marketing jobs by partnering with universities, professional organizations, and agencies. Through Local Service Spotlight, he teaches the Dollar a Day strategy and Content Factory training to help local service businesses enhance their existing local reputation and make the phone ring. Dennis coaches young adult agency owners serving plumbers, AC technicians, landscapers, roofers, electricians, and believes there should be a standard in measuring local marketing efforts, much like doctors and plumbers must be certified.