i was spending way more than i expected on claude code and codex and couldn’t figure out why until i dug into the local session logs. turns out half the context every session was garbage: build artifacts, log directories, generated files, oversized instruction files, repeated tool output, etc. in one repo i had a CLAUDE.md silently loading thousands of tokens into basically every prompt. so i built a local cli to surface all of it. npx getprismo doctor scans your repo + local claude code/codex logs, shows what made sessions expensive, flags token/context waste, estimates avoidable spend, and generates smaller focused context packs so your agent doesn’t have to drag your entire repo into every request. there’s also npx getprismo watch for live monitoring of context spikes, recursive loops, generated artifact leaks, and oversized tool output, plus npx getprismo cc timeline which shows a postmortem timeline of what actually made a session expensive. github: github.com/shanirsh/prismodev would genuinely love feedback on false positives, things it should catch, or workflows that create the most token waste. submitted by /u/Sad_Source_6225
Originally posted by u/Sad_Source_6225 on r/ClaudeCode