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 ictechgy/context-guard --skill optimizegit clone --depth 1 https://github.com/ictechgy/context-guardWrote 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/ictechgy/context-guard/optimize)<a href="https://agentmods.dev/skills/ictechgy/context-guard/optimize"><img src="https://agentmods.dev/badge/skills/ictechgy/context-guard/optimize/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/ictechgy/context-guard/optimize"><img src="https://agentmods.dev/badge/skills/ictechgy/context-guard/optimize.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.00062 | $0.00769 |
| Opus 5.5 | $0.00025 | $0.00308 |
| Sonnet 5.5 | $0.00012 | $0.00154 |
| Haiku 4.5 | $0.00006 | $0.00077 |
Grade B, and why
optimize scanned grade B with 1 finding 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 1mo 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
If installing hook examples, prefer project-local opt-in settings first. Do not silently modify global `~/.claude/settings.json`. What it actually says
ContextGuard
Goal: reduce Claude Code token usage without lowering task success quality.
Use this order:
- Measure before changing behavior.
- Ask the user to run
/usageand/contextif inside Claude Code. - For first-time setup, run
context-guard-setup --planand offercontext-guard-setup --yesfor recommended project-local settings. - If transcript files are available, run
context-guard-audit ~/.claude/projects --top 20 --recommend. - For project configuration/context bloat, run
context-guard-diet scan .. - For structural waste such as duplicate rules, stale import candidates, oversized tool schemas, or repeated reads in local logs, run
context-guard-diet structural-waste . --json.
- Ask the user to run
- Identify the largest bucket:
- stale conversation history -> recommend
/clearbetween unrelated tasks and focused/compactfor long tasks. - startup context -> prune
CLAUDE.md, move long workflows to skills, disable unused MCP servers. - large file reads -> use
context-guard-read-symboland the example Read guard before whole-file context. - very large logs that may need later exact slices -> store sanitized output with
context-guard-artifact storeand query only needed lines/patterns. - noisy command output -> use
context-guard-trim-outputwrappers or the example PreToolUse hook.context-guard-filteris deprecated; do not recommend it. - grep/diff output with possible secrets -> use
context-guard-sanitize-outputor the example Bash hook. - expensive reasoning -> route default work to
sonnetand lower/effort; reserve Opus/opusplanfor planning. - noisy exploration -> keep it local: use
rg,context-guard-read-symbol, artifact queries, or a bounded subagent only when parallel value justifies the multiplier.
- stale conversation history -> recommend
- Produce a minimal action plan with:
- immediate changes,
- config or hook snippets,
- validation command,
- risks and rollback.
- Do not recommend payment/limit bypasses, account sharing, leaked-source patches, or other unsafe/unauthorized methods.
Useful local commands provided by this plugin:
context-guard-audit ~/.claude/projects --top 20 --recommend
context-guard-setup --plan
context-guard-diet scan .
context-guard-diet structural-waste . --json
context-guard-read-symbol path/to/file.py TargetSymbol
context-guard-artifact store --command "long-command" --json < large.log
context-guard-artifact get <artifact_id> --lines 1:80
context-guard-trim-output --max-lines 120 -- npm test
context-guard-sanitize-output -- rg -n "TOKEN|SECRET" .
If installing hook examples, prefer project-local opt-in settings first. Do not silently modify global ~/.claude/settings.json.
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.
- 1mo ago Changed · -2 lines 6b60918eddd1
- 1mo ago First seen · 52 lines · 62 tokens per session scan B 892c1ff650b7
optimize is a skill published in the GitHub repository ictechgy/context-guard (3 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 62 tokens to every session and 769 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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.