{"repo":"egorfedorov/claude-context-optimizer","free":true,"listed":false,"github":"https://github.com/egorfedorov/claude-context-optimizer","clone":"git clone https://github.com/egorfedorov/claude-context-optimizer.git","description":"Claude Code plugin that tracks token usage, identifies wasted context, and saves 30-50% on API costs. Heatmaps, ROI reports, budget alerts, efficiency scores, git-aware suggestions — all local, zero config.","language":"JavaScript","stars":94,"topics":["ai-tools","anthropic","claude-code","claude-code-plugin","cli-plugin","context-management","cost-saving","developer-tools","productivity","token-optimization"],"license":"MIT","category":"productivity","readme_excerpt":"Stop burning tokens on weak prompts and redundant reads. Model-aware for the whole Claude lineup — Fable 5, Opus, Sonnet, Haiku — detected per session, zero config. --- The Problem The average Claude Code session wastes 30-50% of tokens on files that are read but never actually used. Every Read call consumes context — whether the file was relevant or not. - A 200-line config file? 800 tokens gone. - A README you glanced at once? 2,400 tokens burned. - That package.json Claude reads \"just in case\"? 120 tokens, every time. At $5/M input tokens (Opus 4.8), a developer spending $100/month is lighting $30-50 on fire on irrelevant context. The Solution context-optimizer silently tracks every file read, edit, and search. It learns which files are actually useful and which are waste. Over time, it builds a profile of your coding patterns and tells you exactly where your tokens go — and how to stop wasting them. --- What's new in v4.9 — the optimizer learns, and the team shares Your tools now price themselves. MCP and Agent costs were constants someone picked once — mcp ≈ 200 tokens in, Agent ≈ 500. Real results vary by orders of magnitude: a \"list all issues\" query and a one-row lookup are the same tool name and nowhere near the same cost. On MCP-heavy sessions the budget meter was guessing at its own biggest line item. CCO already measured every tool result; now it remembers. After three calls a tool is budgeted from what it actually costs you : Pair it with /cco-overhead mcp : that","default_branch":null,"files":null,"tree":[],"storefront":"/r/egorfedorov","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/egorfedorov/claude-context-optimizer/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}