Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Emasoft/claude-plugins-validation/plugin install 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/commands/emasoft/claude-plugins-validation/cpv-batch-validate-and-fix)<a href="https://agentmods.dev/commands/emasoft/claude-plugins-validation/cpv-batch-validate-and-fix"><img src="https://agentmods.dev/badge/commands/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/commands/emasoft/claude-plugins-validation/cpv-batch-validate-and-fix"><img src="https://agentmods.dev/badge/commands/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.00095 | $0.01978 |
| Opus 5.5 | $0.00038 | $0.00791 |
| Sonnet 5.5 | $0.00019 | $0.00396 |
| Haiku 4.5 | $0.00010 | $0.00198 |
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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/cpv-batch-validate-and-fix — Same-turn validate + verify + fix
For fleet operators who want to apply validation fixes across a
marketplace WITHOUT paying the token cost of the standard
/cpv-batch-validate → /cpv-batch-fix pipeline (which reads every
plugin's source files THREE times — once for validate, once for
fix, once for re-validate), this command runs both phases in one
agent turn per plugin. Each cpv-plugin-fixer-agent subagent reads each
source file ONCE, scans + verifies false positives (via the
v2.100.x AST/schema/markdown classifier) + applies fixes inline.
No intermediate JSON report is written; the per-plugin status JSON
carries the before/after counts.
Per the iron-rule: the same-turn mode is an OPTIMISATION, never a
shortcut. Every finding still goes through the full classifier
chain; FPs are verified via llm-externalizer with file-range
syntax (≤ 200 LOC per call) before being silenced.
Same input grammar as the other batch skills — single plugin /
plugin URL / marketplace local/URL / list / @listfile /
comma-separated.
You are the orchestrator
You — the model running THIS turn — drive the batch. You do NOT fix anything yourself.
Step 0 — Resolve arguments
If no target was given, ask plain-text:
What should I validate-and-fix in one pass? Provide an absolute path, a GitHub URL, a marketplace, or a list file like @/tmp/plugins.txt.
Step 1 — Build the batch plan
BATCH_SPEC="$1"
MAX_PARALLEL=8
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/cpv_batch_orchestrator.py" plan \
"$BATCH_SPEC" \
--agent cpv-plugin-fixer-agent \
--mode batch_same_turn_validate_fix \
--max-parallel "$MAX_PARALLEL"
Capture the orchestrator's stdout. It prints one KEY: value line each
for PLAN, STATUS_TABLE, SESSION_DIR, PLUGIN_COUNT, and
DISPATCH_GROUPS. Bind the two you need downstream:
STATUS_TABLE="$(... STATUS_TABLE line from the plan output ...)"
SESSION_DIR="$(... SESSION_DIR line from the plan output ...)"
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 · 205 lines · 95 tokens per session scan A faab98e98931
cpv-batch-validate-and-fix is a command published in the GitHub repository Emasoft/claude-plugins-validation (4 stars, last pushed 3d ago), licensed MIT. It adds 95 tokens to every session and 1,978 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 commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
auditar-cascading
Invoca cascading-failures-auditor — audita serviço para 5 triggers de cascade (sem timeout, retry sem jitter, sem circuit breaker, sem deadline, queue unbounded) e gera CASCADING-AUDIT.md.
react-native
Command "react-native" from getsentry/toolkit, covering examples, also associate with a release and distribution(s), xcode build step (react-native xcode) and important notes.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.