Pattern: Cross-Tool Token/Cost Observability Is Becoming Its Own Product Category

GitHub·medium signal

As builders spread work across 20–30 coding tools and named model tiers (Sol/Terra/Luna, Opus/Fable/Mythos) with 5×+ cost spreads, standalone spend trackers like codeburn — covering 31 tools by model, project, and task — are emerging as a dedicated layer rather than a per-vendor dashboard feature. The driver is routing: you can't decide when to downshift a task to a cheaper tier without unified cost attribution. Expect this to become a standard part of the agent stack, the way APM did for services.