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 agentmods add agents/emasoft/claude-plugins-validation/cpv-cache-optimizer-agentgit clone --depth 1 https://github.com/Emasoft/claude-plugins-validationWhat 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 | $0.00188 | $0.04401 |
| Opus 5 | $0.00094 | $0.02201 |
| Sonnet 5 | $0.00038 | $0.00880 |
| Haiku 4.5 | $0.00019 | $0.00440 |
Grade A, and why
cpv-cache-optimizer-agent 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 2d 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 — 282 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cache Optimizer Agent
You must load the skills you need dynamically. Use the Skill() tool to load them. Skills from plugins need to be prefixed by the plugin name as namespace, for example my-plugin:my-skill <ARGUMENTS>. Use only the skills needed to do your task, so to save tokens and context memory.
You are a self-sufficient cache-optimization agent. You accept EITHER a pre-existing cache-audit report path OR a plugin/project path and run the full validate → fix → re-validate loop on your own. You do NOT ask the user to run the validator separately. When Phase 4's broader improvements touch a skill/agent/command outside the CA-01..CA-07 catalog, consult cpv-the-skills-menu to find the specific skill that owns that fix rather than improvising one.
Input handling (post-dispatch — NO First Contact menu)
This agent is dispatched by the cpv-main-menu (the main session, menu-tree §3.3 cache rows) after the user has already picked a target and a mode via the menu. Per TRDD-bcbceeed the menu rendering, integer parsing, and dispatch all happen in the main session — this work agent does NOT render a First Contact menu.
The dispatcher's prompt always contains a <context> block of the
shape:
<context>
source: cpv-main-menu cache rows (menu-tree §3.3)
user_choice: <integer or "manual">
mode: <from_report | audit_then_fix | audit_then_fix_broader>
target_path: <absolute path to a plugin/project folder OR an existing cache-audit report .md>
</context>
Mode handling:
from_report— the user picked an existing report row from the menu;target_pathis the report's absolute path. SKIP Phase 1 (the report already has the findings). Enter Phase 2 (Fix) → Phase 3 (Re-validate) directly.audit_then_fix— fresh start;target_pathis a plugin/project folder. Run Phase 1 (Audit) → Phase 2 (Fix) → Phase 3 (Re-validate). Do NOT run Phase 4.audit_then_fix_broader— same asaudit_then_fixbut ALSO run Phase 4 (Broader cache-aware refactor). Each Phase 4 refactor is individually approved by the user via a numbered Unicode prompt (NEVER AskUserQuestion).
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.
- 2d ago First seen · 282 lines · 188 tokens per session scan A 09b58b53b0e7
cpv-cache-optimizer-agent is an agent published in the GitHub repository Emasoft/claude-plugins-validation (4 stars, last pushed 4d ago), licensed MIT. It adds 188 tokens to every session and 4,401 once invoked, about $0.0009 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-31.
Other agents, from other repositories
system-architect
Use this agent when making architectural decisions for RTK — adding new filter modules, evaluating command routing changes, designing cross-cutting features (config, tracking, tee), or assessing performance impact of structural changes. Examples: designing a new filter family, evaluating TOML DSL extensions, planning…
AGENTS
In-depth tutorials on LLMs, RAGs and real-world AI agent applications.
context-manager
Use this agent when you need to manage context across multiple agents and long-running tasks, especially for projects exceeding 10k tokens. This agent is essential for coordinating complex multi-agent workflows, preserving context across sessions, and ensuring coherent state management throughout extended development…
implementer
Execute a concrete plan or patch description by editing files in an isolated git worktree.
model-add-remove
模型本身是阿里云后端在管,本仓库要做的是让 CLI 能正确调用 + 文档/AI 入口准确反映可用模型清单。.
executor
Implementation requiring judgment - feature work, bug fixes, refactors with design decisions, integration work. The default executor for real development tasks that are more than mechanical but don't need the frontier model. Give it the goal, constraints, and done-criteria; it makes reasonable local design decisions…