A three-line prompt tweak quietly raised token spend 30% in one week
Illustrious-Second-7 · reddit · 2026-07-23
A team found that a three-line prompt change had raised their token bill by 30% week over week.
What happened
- Traffic, retries, agent loops, and max tokens were all stable.
- The culprit was three example outputs added to a system prompt to fix a rare formatting edge case.
- Those examples were prepended to every request, even though the bug only appeared in about 1 in 200 calls.
Why it took a week
The only reliable clue was comparing the current system prompt with the version from the previous week and spotting exactly what text had been added. Without prompt version history, the team only saw a rising bill, not the source of the regression.
Fix and takeaway
They moved the examples behind a condition so they only load when needed, which brought spending back to baseline.
The post argues that prompts should be treated like code: prompt edits are cost changes, and prompt versions need diffable history if teams want to attribute spend regressions.
More from coding & agent
- agents-best-practices: a provider-neutral Agent Skill for designing and auditing agentic harnesses — tom_doerr · 2026-09-11
- Cognition's SWE-2 uses a KKT duality argument in RL to shift the effort Pareto curve — YouJiacheng · 2026-09-11
- First-ever Three.js Conference lands in Paris, with a panel on AI-shortened design workflows — OdinLovis · 2026-09-11
- Data engineering, not agent frameworks, is the real bottleneck for enterprise AI agents — dhruv2038 · 2026-09-11
- RTK Terminal Compression Cuts Tokens but Leaves Your AI Coding Bill Unchanged — Bartaseth · 2026-09-11
- GPT-6 Astra beats Factorio with enemies in 44 in-game hours at ~$4,500 API cost — liminal_bardo · 2026-09-11