| name | kco |
| description | Context Control Center — one screen for budget, tokens saved, waste, last prompt grade, the active task, and ready-to-run optimization actions |
| whenToUse | When the user runs /kco, asks for the context dashboard, token budget status, or an overview of session efficiency |
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 ${KIMI_SKILL_DIR}/../../src/dashboard.js board
This renders, in one screen:
- Budget — % of the effective context window used (real usage from wire.jsonl) + $ spent this session when pricing is configured
- Saved — tokens the Read Cache blocked → net savings this session
- 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 /kco-pack
Present the board as-is. Then, based on what it shows:
- If an action line suggests dropping cold files, offer to run
/compact.
- If no task is active, suggest
/kco-task add "<what they're working on>" so
the board can attribute tokens per task.
- If the prompt grade is low (C/D/F), suggest
/kco-coach.
2. (Optional) per-file heatmap
If the user wants the file-by-file breakdown:
node ${KIMI_SKILL_DIR}/../../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 /kco again to see the board fill in."
