Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Emasoft/claude-plugins-validationnpx agentmods add skills/emasoft/claude-plugins-validation/cpv-batch-fix-protocolWrote 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-batch-fix-protocol)<a href="https://agentmods.dev/skills/emasoft/claude-plugins-validation/cpv-batch-fix-protocol"><img src="https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-batch-fix-protocol/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/emasoft/claude-plugins-validation/cpv-batch-fix-protocol"><img src="https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-batch-fix-protocol.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.00082 | $0.01764 |
| Opus 5.5 | $0.00033 | $0.00706 |
| Sonnet 5.5 | $0.00016 | $0.00353 |
| Haiku 4.5 | $0.00008 | $0.00176 |
Grade A, and why
cpv-batch-fix-protocol 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 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.
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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cpv-batch-fix-protocol
Overview
/cpv-batch-fix slices a plugin's validation findings into parallel-fix
shards and dispatches N cpv-plugin-fixer-agent agents from the main session —
one per shard, each with a fresh context window whose size depends on
cpv-plugin-fixer-agent.model (per-model — never assume a fixed limit). This
skill documents the data contract that ties the planner, the shard
agents, and the aggregator together. Loaded by cpv-plugin-fixer-agent (when it
sees mode: batch_shard in its context block) and by the
/cpv-batch-fix slash command body.
See JSON schemas for the three file
formats and TRDD-71e68ab5 (design/tasks/TRDD-20260519_114050+0200-71e68ab5-batch-fix-parallel-sharding.md)
for the design rationale.
- Top-level index (
index.json) · 2. Per-shard manifest (shard-K.json) · 3. Per-shard status (shard-K.status.json) · Schema version bumps
Fork vs fresh worker — the token-honest dispatch choice (TRDD-GVMOKJBB)
Fan-out is a LAST resort, not a default (cost ≈ turns × per-turn-context):
- One plugin that fits one context → NO fan-out. Sequential fix-as-you-go in ONE lean fixer (read each file once, fix in the same turn) is cheapest — a single warm context reused. Forking merely for parallelism here costs N× the context (a wall-clock tradeoff, NOT a token saving).
- A plugin that EXCEEDS one context → fan out, and pick the worker by the dispatcher:
subagent_type:"fork"(Agent tool) — ONLY from a LEAN dispatcher that already loaded the exact context the worker needs (the fix skill + the ledger). A fork inherits the dispatcher's WHOLE conversation at cache-read rate, so it pays off only when that conversation is small and relevant. NEVER fork the bloated main session (it carries all of main's skills/MCP/CLAUDE.md forward).- Fresh lean worker + on-disk slice — the correct choice from a bloated/cold context. The
/cpv-batch-fixpath spawns Ncpv-plugin-fixer-agents from the MAIN session, so this is the batch default: hand each worker its shard manifest / ledger slice ON DISK (a file path, not context inheritance) with a curated tool surface (no MCP).
- NEVER a skill
context: fork. That runs a skill in an ISOLATED fresh subagent with no conversation history (docs: skills#run-skills-in-a-subagent) → it COLD-writes cache = wastes tokens. It is the OPPOSITE of the Agent-tool fork despite the shared word.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 First seen · 109 lines · 82 tokens per session scan A 2bd097a50e48
cpv-batch-fix-protocol is a skill published in the GitHub repository Emasoft/claude-plugins-validation (4 stars, last pushed 3d ago), licensed MIT. It adds 82 tokens to every session and 1,764 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
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…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…