Tip: Hunt Token Waste by Auditing Re-Read Files and Low Read-to-Edit Ratios
Developers Digest·medium signal
Run a transcript analyzer like codeburn against ~/.claude/projects/ to surface the two highest-yield waste patterns: files the agent re-reads across sessions (cache or pin them in CLAUDE.md instead) and turns with a low read-to-edit ratio (the agent is exploring when it should be acting). Each flagged pattern maps to a concrete token/dollar saving, turning 'my agent feels expensive' into a specific, fixable line item.