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 skills/emasoft/claude-plugins-validation/cpv-evaluate-agent-variantsnpx skills add Emasoft/claude-plugins-validation --skill cpv-evaluate-agent-variantsgit clone --depth 1 https://github.com/Emasoft/claude-plugins-validationWrote 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/emasoft/claude-plugins-validation/cpv-evaluate-agent-variants)<a href="https://agentmods.dev/skills/emasoft/claude-plugins-validation/cpv-evaluate-agent-variants"><img src="https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-evaluate-agent-variants.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 | $0.00133 | $0.02397 |
| Opus 5 | $0.00067 | $0.01198 |
| Sonnet 5 | $0.00027 | $0.00479 |
| Haiku 4.5 | $0.00013 | $0.00240 |
Grade A, and why
cpv-evaluate-agent-variants 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 5d 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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cpv-evaluate-agent-variants
Overview
Drives scripts/cpv_agent_eval.py, which compares the ORIGINAL agent against any
subset of the three architectures:
| Architecture | skills: lists |
Skills execute in |
|---|---|---|
| ALL-IN-ONE | every skill it needs | the same agent |
| ONE-FOR-ALL | every skill it needs | a separate subagent per skill |
| PLUGIN-OMNI | the plugin's the-skills-menu + the companion |
resolved at runtime from the menu |
They trade in opposite directions — ALL-IN-ONE pays one large cache creation for turn-1 readiness, ONE-FOR-ALL pays more turns for a near-empty context per node, PLUGIN-OMNI pays a menu lookup to keep the prefix tiny — so which one wins is an empirical question about a SPECIFIC agent. Two tiers answer it, and they are kept strictly apart.
The honesty rule that governs every number: a static estimate must never be presented
as a measured result. Every figure carries the tier that produced it — tier1-static
(computed from real files, no model involved) or tier2-live (measured from a real
run). A missing measurement is reported as UNKNOWN with a non-zero exit: never as 0,
never simulated, never folded into a passing result.
Prerequisites
uvon PATH.- The ORIGINAL agent
.mdfile (the baseline every delta is measured against). - Any variant
.mdfiles to compare, normally produced byscripts/convert_agent.py --to all-in-one|one-for-all|plugin-omni. - The skills the agents reference resolvable on disk — either inside the agent's own
plugin (auto-resolved) or passed with
--skills-root. A wrong root makes every preload unresolvable and the cost model vacuous, so a bad root is a hard error. - For the live tier only: a task file and a directory of captured per-run timings.
Instructions
Tier 1 — static cost model (always runs, zero LLM calls)
- Run the script with the ORIGINAL plus every variant file that exists, and select the
rows with
--variants(any subset oforiginal,all-in-one,one-for-all,plugin-omni). "The original vs the two new versions" is--variants original,all-in-one,one-for-all. - Read the per-variant measurements, all taken over the real files:
- cached-prefix tokens — the agent body PLUS the FULL content of every preloaded
skill. A
skills:entry injects that skill's wholeSKILL.mdinto every invocation, so that content IS a prefix cost; listing a skill is never free. - injected tokens per invocation — the preload portion, i.e. what the
skills:list adds on top of the body, and what would vanish if the same skill were reached at runtime instead. - tool-schema surface — the count of declared tools, or
inheritedwhen the agent declares notools:field (never reported as a surface of 0). - closure size — files and bytes across every reachable skill's
SKILL.md,references/**andscripts/**. - turn-1 readiness — whether every reachable skill is already in the prefix, or
some arrive only after a
Skillcall. - projected N-turn prefix cost — turn 1 at the cache-write rate, each later turn at the cache-read rate.
- cached-prefix tokens — the agent body PLUS the FULL content of every preloaded
skill. A
- Optional flags:
--skills-root PATH(repeatable),--max-depth N,--turns N(repeatable),--json,--report PATH.
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.
- 5d ago First seen · 177 lines · 133 tokens per session scan A a2562b9b38dd
cpv-evaluate-agent-variants is a skill published in the GitHub repository Emasoft/claude-plugins-validation (4 stars, last pushed yesterday), licensed MIT. It adds 133 tokens to every session and 2,397 once invoked, about $0.0007 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…