Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add egorfedorov/claude-context-optimizer/plugin install 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-shield)<a href="https://agentmods.dev/skills/egorfedorov/claude-context-optimizer/cco-shield"><img src="https://agentmods.dev/badge/skills/egorfedorov/claude-context-optimizer/cco-shield.svg" alt="Measured on agentmods" 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.00023 | $0.00386 |
| Opus 5 | $0.00012 | $0.00193 |
| Sonnet 5 | $0.00005 | $0.00077 |
| Haiku 4.5 | $0.00002 | $0.00039 |
Grade A, and why
cco-shield 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 8d 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.
What it actually says
ContextShield Status
Show the user the current ContextShield protection status and historical waste prevention stats.
Subcommands
If the user asked for suggestions (/cco-shield suggest) or to apply them
(/cco-shield apply), run instead:
node ${CLAUDE_PLUGIN_ROOT}/src/context-shield.js suggest # preview .contextignore candidates
node ${CLAUDE_PLUGIN_ROOT}/src/context-shield.js apply # append them to ./.contextignore
suggest lists files wasted in 3+ sessions as ready-to-use .contextignore
patterns with per-session token savings. apply appends them (deduped against
existing rules) so those reads are blocked permanently. Show the output as-is.
Status report (default)
Run the following command to get pattern data:
node ${CLAUDE_PLUGIN_ROOT}/src/tracker.js patterns
From the patterns data, present:
- ContextShield Status: Active (it's always active as a PreToolUse hook)
- Protected Files: List files with 3+ waste sessions — these trigger warnings before Read
- Tokens Saved: Estimate based on waste history (files that would have been read without shield)
- Co-occurrence Groups: Files that are usually edited together
Format as a clean status report. If no pattern data exists yet, tell the user: "ContextShield is warming up! It learns from your usage patterns and will start giving you smart suggestions after a few sessions."
End the report with:
ContextShield runs automatically on every Read. No configuration needed.
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.
- 8d ago First seen · 48 lines · 23 tokens per session scan A f444894d6d67
cco-shield is a skill published in the GitHub repository egorfedorov/claude-context-optimizer (107 stars, last pushed 6d ago), licensed MIT. It adds 23 tokens to every session and 386 once invoked, about $0.0001 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: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: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.
alive:bundle
Create, share, and graduate bundles — the unit of focused work within a walnut. Manages the full bundle lifecycle from creation through sharing to graduation.
alive:settings
The human wants to adjust how the system behaves — not what it contains, but how it feels. Voice, rhythm, preferences, walnut-level config, full permissions toggleable, named squirrel config, action logging toggle. The system adapting to them. Routes to preferences.yaml or walnut config.yaml depending on scope. For…
alive-cleanup
System maintenance -- stale tasks, orphan folders, unsaved sessions, world health check.
alive-daily
Morning operating system -- sync inputs, read everything, surface priorities, show the day.