Patriola's Guide to Claude: Token Budgets: Control What Your Claude Sessions Actually Cost

Every Claude Code session burns tokens. Most operators don't know how many until the quota runs out.

This book builds the cost-control layer for CLI operators — the people running Claude Code directly, not the SDK. It is not about API-level prompt caching. Chapter 1 says so plainly, explains what prompt caching is and why it doesn't apply here, and moves on to what does: the three levers a CLI operator actually controls. From there, seven chapters each deliver one working piece of the cost-control stack.

Chapter 2 shows how to read what sessions actually cost, building a session cost log that makes spend visible. Chapter 3 turns the PreCompact baton into a cost gate — the hook that fires when context approaches the window limit becomes the moment you decide whether to continue or stop. Chapter 4 builds a model router that sends work to the right tier: Haiku for lookups, Sonnet for standard tasks, Opus for work that earns the price. Chapter 5 installs budget gates that stop pipelines before they blow the cap — a hard stop, a soft warning, and a config file that sets the thresholds. Chapter 6 separates cost by project, so one runaway job can't drain the quota for everything else. Chapter 7 ties the pieces together into a cost-aware pipeline design — the habits and structural patterns that keep spend predictable across every session you run.

By the last chapter you have a cost-control stack running beneath your workflows. Spend is visible, routed, and bounded. The quota surprise stops.