Every Claude Code session I opened in July began the same way. Claude Fable 5 took the driver’s seat, effort pinned at ultracode, and the first thing I typed was /mission-command. Thirty-one days of that habit deserved a number, so on August 4 I opened one more Fable session and asked it to read the meters on both machines I had run it from.
Some context for anyone arriving cold. Mission-command is a Claude Code skill I wrote on July 4, 2026, midway through my first metered week with Anthropic’s newest frontier model. It is open source under the Apache license and installs as a Claude Code plugin. The skill borrows a doctrine from military staff work: a commander states intent and keeps hold of the decisions that are expensive to get wrong, and the units in the field do the work inside that intent. In my setup the commander is Fable 5, the frontier tier Anthropic sells above Opus at $10 per million input tokens and $50 per million output. The field units are subagents running Claude Sonnet 5 and Claude Opus, which cost a fifth and a half of Fable’s rate. The Opus seat ran 4.8 for most of the month and moved to Opus 5 on July 24, at the same price. Ultracode is the session mode that lets the commander spawn those workers by the dozen.
Reading the meter
Claude Code writes a transcript of every session to disk, subagent sessions included, and each assistant turn in those files carries its exact token counts. Fable wrote the analysis scripts and ran the whole investigation itself: it parsed the 3,261 transcript files across the two machines, 1.4 GB in all, kept the 77,592 turns stamped July 2026, dropped the duplicate entries that streaming produces, and priced what remained against Anthropic’s published API rate card. The cache rates matter more than the headline rates for this kind of workload, and it applied the full card: cache reads at a tenth of the input price, and cache writes at 1.25 times it for the five-minute tier or double for the one-hour tier.
July came to $6,648.02 in API-equivalent spend. The two machines landed within nine dollars of each other, $3,319.59 and $3,328.43, despite carrying different projects on different daily rhythms. That closeness tells me the pattern reproduces.
| Model | Rate ($/MTok, in/out) | Turns | Output tokens | Cost |
|---|---|---|---|---|
| Claude Fable 5 | 10 / 50 | 7,231 | 9.89M | $2,879.06 |
| Claude Opus 4.8 | 5 / 25 | 13,927 | 8.63M | $1,990.13 |
| Claude Sonnet 5 | 2 / 10 (intro) | 53,497 | 4.03M | $1,648.20 |
| Claude Opus 5 | 5 / 25 | 1,172 | 0.50M | $115.55 |
| Claude Haiku 4.5 | 1 / 5 | 1,765 | 0.01M | $15.08 |
I pay $200 a month for the Max 20x subscription. The same tokens on pay-as-you-go credits would have billed thirty-three times the subscription price, and the plan had paid for itself by July 4.
Where the turns ran
The transcripts distinguish main-session turns from subagent turns, and the split reads like an org chart. Fable logged 7,231 turns and 83 percent of them sat in main sessions, holding the plan. Of Sonnet’s 53,497 turns, 98.4 percent ran inside subagents.
| Model | Main session | Subagents |
|---|---|---|
| Claude Fable 5 | 6,024 turns · $2,666 | 1,207 turns · $213 |
| Claude Opus 4.8 | 3,370 turns · $1,021 | 10,557 turns · $969 |
| Claude Sonnet 5 | 833 turns · $59 | 52,664 turns · $1,589 |
| Claude Opus 5 | 456 turns · $63 | 716 turns · $53 |
| Claude Haiku 4.5 | - | 1,765 turns · $15 |
Fable held nine percent of the month’s turns and wrote 43 percent of its output tokens. Those 9.89 million tokens are the plans and the finished deliverables, the work I wanted frontier judgment on. The volume went downstream: 86 percent of all turns ran inside subagents on cheaper tiers.
Repricing the month
Claude Code fans out subagents for anyone. On its defaults, the workers take the model already in the chair, so a Fable session breeds Fable workers at Fable prices. Mission-command supplies the staffing policy: it carries a tier map and sends each dispatch to the cheapest model fit for the job, holding Fable back for the decisions where judgment compounds.
That default is the counterfactual I care about, the one where I skip the skill and let Fable do everything itself, since Fable is where every session started. Billing July’s full token volume at Fable’s rates gives $15,482. The fleet ran the same volume for $6,648, which keeps $8,834 in the account, a 57 percent cut. A milder counterfactual prices everything at Opus 4.8 rates and lands at $7,741, so the routing beats even a sensible mid-tier default while keeping frontier judgment in the loop the whole time.
Per unit, the spread is wide. Fable’s own main-session turns cost $0.44 each. Blended across all 77,592 turns, the fleet’s average was $0.09. mission-command bought Fable’s decision quality at close to Sonnet’s unit price, and it did so twice, on two machines whose workloads never touched.
The credit ledger
I want the credit ledger clean, because one discount in this data is easy to misattribute. Without prompt caching, July’s tokens would have billed $38,356 fresh. That 83 percent reduction comes from Claude Code’s own harness, which sets cache breakpoints for every user automatically, so the platform earns that credit. Fan-out even has a cache cost of its own: each fresh subagent pays the 1.25x write premium before it reads anything from the cache, and cache writes made up a third of my bill.
The routing is the skill’s own work. Sonnet and Haiku handled 71 percent of all turns for 25 percent of the cost, and repricing just their workload at Opus rates adds about $2,500 back onto the bill. That matches what I measured the week I adopted the skill, when the premium-model share of my tokens fell from 67 percent to 29 percent.
There is one more thing the repricing hides. It assumes the same 77,592 turns could have run one after another on a single frontier context. The fleet moved 9.7 billion context tokens across 28 active days, and much of that happened while I was away from the keyboard or asleep, with up to twenty-some workers in flight at once.
The subscription’s own meters make the same point. Max measures usage weekly, and Fable may take at most half of the all-model allowance, so a solo Fable month parks the other half of the subscription unused no matter how hard it runs. The fleet drained both pools. Week after week I closed at around 95 percent of the Fable allowance and around 95 percent of the overall allowance, with Fable’s half going to judgment and the worker tiers spending the rest.
The dividend
Sonnet’s introductory pricing dies on August 31, and at standard rates July restates to $7,472. On September 1 I’ll hand Fable the meters again.
But the number I keep coming back to isn’t the $8,834 the fleet kept in the account. It’s the shape of the month itself: 77,592 turns, 9.7 billion tokens of context, most of it moving while I slept. At fleet prices, that month cost me $200. Run serially on the model that made every decision in it, the month doesn’t get slower or pricier - it stops existing. Half the subscription sits unreachable, the queue outlives the quota, and no budget buys a second thread on a single mind.
That’s the orchestration dividend. Not a discount - a month you couldn’t otherwise have.
The views expressed here are my own. The measurements describe my personal Claude subscription usage and do not represent any organization, product, or system.