Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/egorfedorov/claude-context-optimizernpx agentmods add skills/egorfedorov/claude-context-optimizer/cco-configWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/egorfedorov/claude-context-optimizer/cco-config)<a href="https://agentmods.dev/skills/egorfedorov/claude-context-optimizer/cco-config"><img src="https://agentmods.dev/badge/skills/egorfedorov/claude-context-optimizer/cco-config/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/egorfedorov/claude-context-optimizer/cco-config"><img src="https://agentmods.dev/badge/skills/egorfedorov/claude-context-optimizer/cco-config.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00034 | $0.00853 |
| Opus 5 | $0.00017 | $0.00426 |
| Sonnet 5 | $0.00007 | $0.00171 |
| Haiku 4.5 | $0.00003 | $0.00085 |
Grade A, and why
cco-config scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CCO Config — tune how aggressive the optimizer is
CCO's behavior knobs used to be magic numbers spread across four modules.
This surfaces them, range-validated, in ~/.claude-context-optimizer/config.json
under thresholds.
The plugin root is the directory containing src/config.js. Run everything
from there.
Parse $ARGUMENTS:
show (or no arguments)
node src/config.js
Print the table as-is. * marks values the user set; ! marks a stored value
that failed validation and is being ignored in favour of the default. If any
! rows appear, point them out — a typo there means a knob silently isn't
doing what the user thinks.
get <key>
node src/config.js get <key>
set <key> <value>
node src/config.js set <key> <value>
Exits non-zero with the valid range on a bad value or unknown key — relay that message rather than guessing a correction. After a successful set, say which behavior it changes (see the table below), because the effect is not obvious from the key name alone.
reset [key]
node src/config.js reset <key> # one key
node src/config.js reset # everything back to defaults
Resetting everything discards all the user's tuning — confirm first unless they were explicit ("reset all", "вернуть всё по умолчанию").
The keys
| Key | Default | What it changes |
|---|---|---|
rereadWarnAt |
3 | reads of an unedited file before the first re-read warning |
rereadEscalateAt |
5 | reads before the "put it in CLAUDE.md" escalation |
bigFileLines |
500 | full-read line count that triggers the offset/limit warning |
mediumFileLines |
200 | full-read line count that triggers the soft hint |
staleTokenRatio |
0.10 | share of budget loaded after a file before Read Cache re-allows it |
staleFiles |
8 | other files loaded after a file before it counts as evicted (at 200K) |
staleTimeMs |
600000 | ms since last read before a cached file counts as stale |
promptMinWords |
8 | word count below which the coach calls a prompt too vague |
promptIdealMaxWords |
200 | upper bound of the coach's "ideal length" band |
promptTooLongWords |
500 | word count above which the ask is considered buried |
packBudgetPercent |
25 | max share of the budget /cco-pack may consume |
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 85 lines · 34 tokens per session scan A bac600444412
cco-config is a skill published in the GitHub repository egorfedorov/claude-context-optimizer (107 stars, last pushed 7d ago), licensed MIT. It adds 34 tokens to every session and 853 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
alive:demo
Generate a believable, lived-in ALIVE world from a free-text persona description (custom path) or a deterministic sandbox preset. Routes the create/list/activate/deactivate/delete/status surface and orchestrates the 5-stage subagent generation pipeline.
alive:system-upgrade
Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.
alive:save
The human wants to checkpoint. Or: the stash has grown heavy — 5+ items, 30+ minutes, a natural pause in the work. The squirrel doesn't decide when to save. It surfaces the need and lets the human pull the trigger. Runs the full save protocol: confirms stash, writes log, updates state, generates projections…
alive:system-cleanup
The world feels messy. Stale tasks, orphan folders, v2 remnants, unsaved sessions — entropy is accumulating and needs to be addressed before it compounds. Scans across all walnuts, then surfaces issues one at a time.
alive:create-walnut
Something new is emerging. A venture, an experiment, a person entering the orbit, a life area getting serious. It needs its own walnut — its own identity, history, and future. Scaffolds the full structure, maps existing context sources, and optionally migrates files across.
alive:session-history
Revive sessions (quick or heavy), browse, and search — 'what happened recently?', 'find the session where we discussed X', 'revive yesterday's session'. For single-session recall and multi-session browsing. If the human needs to merge multiple sessions into one working context or detect conflicts between parallel…