SkillsAdd

egorfedorov/claude-context-optimizer

cco

Context Control Center — one screen for budget, $ spent, tokens saved, waste, last prompt grade, the active task, and ready-to-run optimization actions

First seen Mar 23, 2026

Installation

$ npx skills add egorfedorov/claude-context-optimizer --skill cco
View on skills.sh ↗ GitHub repository ↗

Also in this package

Other skills from egorfedorov/claude-context-optimizer · top by installs.

npx skills add egorfedorov/claude-context-optimizer
cco-claudemd 228 smart-loader 182 cco-budget 180 cco-report 177 cco-anatomy 173 cco-clean 172 cco-digest 170 cco-git 169 cco-templates 167 cco-export 166

Browse all from egorfedorov/claude-context-optimizer

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 107
License LICENSE
Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

LicenseMIT
Allowed toolsBash, Read

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,767 B
  • docs SUMMARY.md 164 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 218 installs

SKILL.md

Context Control Center

The all-in-one view of the current session. Show the user the live board, then the per-file heatmap if they want detail.

1. Show the board

node ${CLAUDE_PLUGIN_ROOT}/src/dashboard.js board

This renders, in one screen:

  • Budget — % of the effective context window used + $ spent this session
  • Saved — tokens the Read Cache blocked → the effectiveness multiplier (e.g. "1.4x")
  • Waste — cold context (read but never edited) you can drop to free budget
  • Prompt — grade of the last prompt (from Prompt Coach)
  • Task — the active task and its token/$ cost (per-task attribution)
  • Actions — concrete next steps: what to drop → /compact, what to /cco-pack

Present the board as-is. Then, based on what it shows:

  1. If an action line suggests dropping cold files, offer to run /compact.
  2. If no task is active, suggest /cco-task add "<what they're working on>" so

the board can attribute tokens per task.

  1. If the prompt grade is low (C/D/F), suggest /cco-coach.

2. (Optional) per-file heatmap

If the user wants the file-by-file breakdown:

node ${CLAUDE_PLUGIN_ROOT}/src/tracker.js heatmap

Highlight files read but never used (waste), files that were edited (high-value), and the total token usage / waste percentage.

If there is no data yet, tell the user: "No data in this session yet — keep working. Reads, edits, prompts and cache savings are tracked automatically; run /cco again to see the board fill in."