The Economics of Claude Code
The expensive thing is never the prompt you write. It's the context you carry. Every habit in this series is about the same principle: keep the context lean, keep the cache warm, and when a session has served its purpose, let it go.
- OverviewThe Economics of Claude Code: Where the Money Actually GoesThe full picture: 10 cost drivers, pricing mechanics, benchmarks, and the rhythm of cost-efficient Claude Code work.
- Part 1The Idle TaxCache gaps cost 12.5×. Every time you step away, the meter resets.
- Part 2The "Just One More Turn" TrapContext rot is superlinear. Past the knee, you pay more to carry old context than to do new work.
- Part 3The Agent That Read 200 FilesSubagents are context firewalls. Exploration belongs in a disposable window.
- Part 4The Compact GambleAuto-compact is lossy summarization at peak context. Sometimes it drops the one constraint you needed.
- Part 5The Watching CostTool output is permanent. Every dump gets reprocessed on every turn for the rest of the session.
- Part 6The Delegation TaxSubagent results are permanent too. The agent's context is disposable. Its result is not.
The Companion Helpers
Each post comes with a local hook that makes the cost driver visible at the moment it happens. All six helpers (plus an effort-control patch for Opus 4.7) are in zivtech/claude-cost-helpers on GitHub. GPL-3.0-or-later licensed.
git clone https://github.com/zivtech/claude-cost-helpers
cd claude-cost-helpers
./install-all.shOr install via the skills.sh registry:
npx skills add zivtech/claude-cost-helpersThe Common Thread
Six cost drivers, six habits, six open-source helpers. Concrete numbers, real workflows, and the pricing mechanics that make some habits expensive and others cheap.