Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add egorfedorov/claude-context-optimizer --skill cco-orchestrategit clone --depth 1 https://github.com/egorfedorov/claude-context-optimizerWrote 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-orchestrate)<a href="https://agentmods.dev/skills/egorfedorov/claude-context-optimizer/cco-orchestrate"><img src="https://agentmods.dev/badge/skills/egorfedorov/claude-context-optimizer/cco-orchestrate/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-orchestrate"><img src="https://agentmods.dev/badge/skills/egorfedorov/claude-context-optimizer/cco-orchestrate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00037 | $0.00517 |
| Opus 5.5 | $0.00015 | $0.00207 |
| Sonnet 5.5 | $0.00007 | $0.00103 |
| Haiku 4.5 | $0.00004 | $0.00052 |
Grade A, and why
cco-orchestrate 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 today.
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.
What it actually says
Orchestrate: $ARGUMENTS
Needs Claude Code or Cowork: the
scoutandrunnersubagents don't load in claude.ai chat. There, do the task directly and suggestfresh-startwhen the conversation gets long.
Do this task as an orchestrator. The aim is the same result at a fraction of the cost: in a long session, every token in this conversation is re-read on each later request, while a subagent's reading is discarded when it returns. The plugin's subagents run on Haiku 5.5, about 40× cheaper per token than Opus 5.5.
How to split the work
- Understand (delegate). List the questions you need answered before you
can change anything: where is X defined, how does Y flow, what calls Z,
what do the docs say about W. Send each independent question to a
context-optimizer:scoutsubagent, several in parallel when they don't depend on each other. Write each prompt as a precise question with the names, paths or URLs you already know, and ask forpath:lineevidence. - Decide (yourself). Plan from the scouts' answers. Read yourself only the exact line ranges you are about to edit.
- Change (yourself). Make the edits here. Don't hand edits or design decisions to a subagent.
- Verify (delegate). Send the exact test, build or lint commands to a
context-optimizer:runnersubagent and act on its failure report. Fix, then send the runner again until it passes. - Report. What changed, why, and what was verified.
When not to delegate
- One known file or one grep: do it yourself; a subagent's startup costs more.
- Work that needs many back-and-forth steps on shared context.
- Anything that changes files, or needs judgment about the design.
If this conversation is already past ~150K tokens, suggest /compact before
starting a large task.
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.
- today First seen · 44 lines · 37 tokens per session scan A 0dea67dc05b0
cco-orchestrate is a skill published in the GitHub repository egorfedorov/claude-context-optimizer (116 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 517 once invoked, about $0.0001 per session on Opus 5.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-10-17.
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: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…
alive:world
The human doesn't know what to work on, or wants to see everything at once. They need the big picture — what's active, what's stale, what needs attention. Renders a live world view grouped by ALIVE domain, then routes to open, tidy, find, history, or map.