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 Emasoft/claude-plugins-validation --skill cpv-batch-fixgit 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-batch-fix)<a href="https://agentmods.dev/skills/emasoft/claude-plugins-validation/cpv-batch-fix"><img src="https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-batch-fix/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"><img src="https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-batch-fix.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.00096 | $0.01181 |
| Opus 5.5 | $0.00038 | $0.00472 |
| Sonnet 5.5 | $0.00019 | $0.00236 |
| Haiku 4.5 | $0.00010 | $0.00118 |
Grade A, and why
cpv-batch-fix 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cpv-batch-fix
Overview
Parallel fix skill for one OR many plugins. Two dispatch shapes:
-
Single plugin (default — backward-compatible with v2.91.0): shards the plugin's findings into ~15-finding groups and dispatches one
cpv-plugin-fixer-agentper shard, all in parallel. This is the original/cpv-batch-fixbehaviour and still applies. -
Marketplace / list (NEW in v2.101.0): resolves the spec via
scripts/cpv_marketplace_input.py, then dispatches onecpv-plugin-fixer-agentper plugin from a single main-session message. Each per-plugin agent runs the standard fix loop on its assigned plugin — including its own internal sharding if its finding count justifies it.
The orchestrator body lives in this plugin's
commands/cpv-batch-fix.md slash-command file.
Prerequisites
claude-plugins-validationplugin installed (providesscripts/cpv_batch_planner.py,scripts/cpv_batch_aggregator.py,scripts/cpv_marketplace_input.py,scripts/cpv_batch_orchestrator.py, and thecpv-plugin-fixer-agentagent).- For URL inputs:
giton PATH and network access togithub.com. - Write access to every plugin's tree — this skill MUTATES source files in place.
- Each plugin should be a clean git working tree (committed or stashed) before the run so the per-plugin fixer's commits are inspectable.
Inputs
| Shape | Behaviour |
|---|---|
| Single plugin (local) | Per-shard fan-out (existing v2.91.0 path) |
| Single plugin (URL) | Clone + per-shard fan-out |
| Marketplace (local) | Per-plugin fan-out (NEW) |
| Marketplace (URL) | Clone every plugin + per-plugin fan-out |
List (CLI / @listfile / comma-separated) |
Per-plugin fan-out |
Knobs (forwarded to the orchestrator):
--shard-size N(default 15) — per-plugin shard size--max-parallel N(default 8, cap 16) — max concurrent agents--min-severity LEVEL(defaultminor) — drop findings below
Instructions
- Determine whether the user's spec is a single plugin or a marketplace/list. The command body does this via the resolver; agents can dispatch the command directly.
- Invoke the slash command body:
/cpv-batch-fix <user's spec> [--shard-size N] [--max-parallel N] [--min-severity LEVEL] - For single-plugin inputs, the orchestrator runs the existing per-shard protocol (TRDD-71e68ab5).
- For marketplace/list inputs, the orchestrator runs the
per-plugin protocol (TRDD-3dcbb37c) — one fixer per plugin in
batch_per_pluginmode applied to the WHOLE plugin (each fixer's internal sharding kicks in when finding-count justifies it). - The user gets a status table + final summary.
What ships with it
1 file 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 · 111 lines · 96 tokens per session scan A 7d5ff9dfb2b5
cpv-batch-fix is a skill published in the GitHub repository Emasoft/claude-plugins-validation (4 stars, last pushed 3d ago), licensed MIT. It adds 96 tokens to every session and 1,181 once invoked, about $0.0004 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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
deck-retro
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…