Skip to content

Claude Code

Claude Code Ultra week measured at 17B Opus cache reads

5 min read

Our AI analyst checked this story itself: it ran, measured and compared against the originals. What we checked

Written by an AI model from the linked sources and checked against them by a second model. How we work

All about: Claude Code versions and changes →
Image: atlas-ade.dev

Atlas-ade’s field guide to Claude Code plan usage, last checked against a live meter on October 29, puts a week on the Ultra plan (formerly Max 20x) at 17B Opus cache-read tokens and finds the costly turn is the cold one: at 800k context, a turn that has to rewrite the cache moves the meter about 23 to 27 times as far as a warm one. Only Ultra is measured, on one account’s long agentic coding, so the guide’s Pro and Max figures are estimates derived from it.

A turn goes cold after a long pause, a compaction or a model switch. On a plan, Claude Code keeps the main conversation’s cache for an hour, but subagents get five minutes unless you set their TTL. On an API key the default is five minutes unless you change it.

What a turn costs

For one Opus turn with 2,000 output tokens, the guide’s tables put a warm turn at 200k context at 0.004% of an Ultra week, about 24,000 such turns, and a cold one at 0.046%, about 2,200. At 800k context a warm turn is 0.008% (about 13,000 a week) and a cold one 0.176% (about 570). The page’s calculator shows two figures where its model can’t yet decide between two readings; the tables print only the first.

Cache reads are the figure the fit pins down best. Output is the least certain part of it.

What 1% of an Ultra week buys

The meter weighs four kinds of token very differently. One percent of an Ultra week equals about 660k Opus output tokens, 3M input tokens, 170M cache-read tokens or 4.6M cache-write tokens, each spent alone. At API list prices that is about $13 of output, $12 of input, $35 of cache reads and $37 of cache writes at the one-hour price, or $23 at the five-minute price. A full week comes to roughly $1,200 to $3,700 of Opus 5.5 at list prices. By our recomputation, the low end is a week spent only on input and the high end a week spent only on one-hour cache writes; cache reads alone come to $3,477.

Sonnet tokens go further on the meter: 1.1M output or 290M cache reads per 1%. Fable 5.1 goes much less far, 160k output or 41M cache reads, and the guide marks that column an estimate. Fable 5.2, released November 9, is 20% cheaper than 5.1 at API prices, but its plan weight isn’t measured yet. The page’s parameters give Fable a meter weight of 4.25 to 4.5 times Opus, while at list prices Fable 5.1 costs 2.5 times Opus 5.5, so by the guide’s estimate a Fable token moves the weekly meter 1.7 to 1.8 times further than its price ratio to Opus would. Anthropic’s help pages also give Max and Ultra a separate weekly limit for Fable; how it interacts with these weights is documented, not measured.

Pro and Max, by derivation

In the guide’s plan table, Pro at $20 a month holds 1.7B Opus cache-read tokens a week and 220M in one five-hour window. Max (formerly Max 5x) at $100 holds 8.7B and 1.1B. Ultra at $200 holds 17B, with no five-hour limit on verified accounts since October 31. Pro and Max are Ultra scaled by the plan-size ratios in u/flobernd’s subscription cost model, because Anthropic publishes no fixed allowance, only relative scale: Max is 5x or 20x Pro. That derivation makes Ultra’s week about twice Max’s, while one team pooling subscriptions found the gap between Max 20x and Max 5x weekly capacity down to about 1.5x in September.

On Pro and Max the five-hour window works as a speed limit inside the week. Measured on Ultra before October 31, the same work moved it about 3.96 times as far as the weekly meter, so a full five-hour window was about 25% of a week.

Our analysis

What we checked

On November 12 we recomputed the guide’s dollar column from Anthropic’s pricing page, extracted the two parameter sets from the page’s calculator and ran it once in headless Chromium, and re-ran the headless measurement the guide cites from a fresh clone of claude-usage-tracker.

How we check stories

The dollar figures hold: Opus 5.5 bills cache reads at 0.05 times the input price, $0.20 per million tokens, and at the usual 0.1 times the cache-read row would be $69.54. The output and per-turn figures each have a second value under the calculator’s other fit, which differs from the first by 62% on the output weight and 1.2% on the cache weight. And the guide’s claim about headless runs and the weekly meter goes further than the measurement it cites.

FigureSet 1 (the tables)Set 2
Opus output tokens per 1% of a week660k ($13.23)1,072,409 ($21.45)
Warm 200k turn, 2,000 out0.004%, about 24,000 a week0.00303%, 33,013 a week
Cold vs warm, 200k / 800k11.06x / 23.03x15.03x / 27.06x
Cache reads per 1%173.9M171.8M
  • In the live calculator, 100 warm Opus turns at 200k context with 2,000 out showed 0.30 to 0.42% of a week.
  • The guide says headless runs (claude -p or the Agent SDK) on Pro and Max eat the five-hour window faster while the weekly meter moves much less. The cited tracker covers three Max 20x accounts only, and its data ends October 4, before a change on October 7 its author flags as untested. Our re-run reproduced its 1.53 [1.41, 1.67] over 306 steps, but that is five-hour points per weekly point. Per credit, headless moved the five-hour meter 1.628 times as far [1.356, 1.953] and the weekly meter 1.049 times [0.930, 1.184], an interval that includes 1. The author withdrew the cheaper-on-weekly reading as “a mix effect”, and one account holds 50 of the 58 headless-heavy steps.

No comments yet. Be the first.

Join the conversation

Sign in to leave a comment. It appears after moderation.