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-validate-and-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-validate-and-fix)<a href="https://agentmods.dev/skills/emasoft/claude-plugins-validation/cpv-batch-validate-and-fix"><img src="https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-batch-validate-and-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-validate-and-fix"><img src="https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-batch-validate-and-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.00125 | $0.01308 |
| Opus 5.5 | $0.00050 | $0.00523 |
| Sonnet 5.5 | $0.00025 | $0.00262 |
| Haiku 4.5 | $0.00013 | $0.00131 |
Grade A, and why
cpv-batch-validate-and-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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cpv-batch-validate-and-fix
Overview
Same-turn variant of the parallel validate + fix pipeline. Each
cpv-plugin-fixer-agent subagent reads every source file ONCE, scans +
verifies FPs inline (via the v2.100.x context classifier +
llm-externalizer with file-range syntax — minimum-token FP
verification), applies confirmed-real fixes, and runs one
clean-room re-check.
Same input grammar as
cpv-batch-validate. The
orchestrator body lives in this plugin's
commands/cpv-batch-validate-and-fix.md slash-command file.
Prerequisites
claude-plugins-validationplugin installed (providesscripts/print_menu.py— the claude-menu-system bridge — and thecpv-plugin-fixer-agentagent).claude-menu-systemplugin installed — the slash command emits the status table via its Stop-hook (throughscripts/print_menu.py). Declared as a hard dependency in CPV'splugin.json;print_menu.pyfails fast with an install hint if missing (there is no inline fallback renderer — TRDD-4de479a0).- LLM Externalizer MCP available (it's the FP verifier for uncertain findings — without it the agent falls back to keeping the finding at the classifier's verdict).
- Write access to every plugin's tree — this skill MUTATES source files in place.
- For URL inputs:
giton PATH and network access togithub.com.
Inputs
See the cpv-batch-validate input table — every shape is supported identically.
Instructions
- Confirm the user wants the same-turn variant (faster, narrower
visibility) vs the separate-pass pipeline (slower, more
intermediate reports). When in doubt, route to
cpv-batch-validate+cpv-batch-fixseparately. - Invoke the slash command body:
/cpv-batch-validate-and-fix <user's spec> [--max-parallel N] - Each per-plugin agent runs in
batch_same_turn_validate_fixmode. The agent reads each source file ONCE, scans + verifies FPs + fixes inline, then runs the final clean-room re-check. The command aggregates the per-plugin status JSONs into a CMS-shaped status-table spec, queued viascripts/print_menu.py; the claude-menu-system Stop hook emits the Unicode-bordered table post-turn viasystemMessage(zero token cost — never enters the agent transcript). NEVER print the table inline. - The user gets the final status table (emitted by the Stop hook) +
a one-line summary
(
DONE: plugins=N clean=X fixed=Y partial=Z failed=W. Total FPs verified: F).
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 · 116 lines · 125 tokens per session scan A 8fd611be34e0
cpv-batch-validate-and-fix is a skill published in the GitHub repository Emasoft/claude-plugins-validation (4 stars, last pushed 3d ago), licensed MIT. It adds 125 tokens to every session and 1,308 once invoked, about $0.0005 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
adk-go-self-review
Review an ADK Go change the way a maintainer will — a fresh-context pass over the whole diff, five lenses (correctness and tests, scope, simplicity, style, adk-python parity), and the mutation check that proves your tests pin the change. Use before opening a PR, before any later push that changes code, and when asked…
adversarial-reviewer
Stress-test a code change for concrete correctness defects, unsafe assumptions, and failure modes. Use when the user explicitly asks for an adversarial review, a deep bug hunt, or to tear a change apart, or to check your own change before submitting it. Do not use for ordinary review, style feedback, or general…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
semgrep-rule-variant-creator
Creates language variants of existing Semgrep rules. Use when porting a Semgrep rule to specified target languages. Takes an existing rule and target languages as input, produces independent rule+test directories for each language.
brooks-sweep
Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user…
plugin-review
Review plugin quality with tiered checks and dependency scoping. Use for PR and pre-release audits.