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-full-scan-and-fix)<a href="https://agentmods.dev/commands/emasoft/claude-plugins-validation/cpv-batch-full-scan-and-fix"><img src="https://agentmods.dev/badge/commands/emasoft/claude-plugins-validation/cpv-batch-full-scan-and-fix.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.1 | $0.00109 | $0.02323 |
| Opus 5 | $0.00055 | $0.01162 |
| Sonnet 5 | $0.00022 | $0.00465 |
| Haiku 4.5 | $0.00011 | $0.00232 |
Grade A, and why
cpv-batch-full-scan-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 6d 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 — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/cpv-batch-full-scan-and-fix — Maximum-coverage same-turn sweep
For fleet operators who want the deepest possible parallel sweep
across every plugin in a marketplace, this command bundles
validate + security + caching audit + caching optimize + FP
verification + fix into ONE per-plugin agent turn. Each
cpv-plugin-fixer-agent subagent reads each source file ONCE and triggers
every applicable in-process checker, classifies findings via the
v2.100.x context classifier, verifies uncertain findings via
llm-externalizer with file-range syntax (≤ 200 LOC per call),
applies confirmed-real fixes inline, then runs a clean-room
re-check.
The four separate batch skills run separately would read every source file 4× (once per scan type) plus the fix pass — this command does it in one pass.
Per the iron-rule: same-turn = optimisation. Every finding still walks the full classifier chain; FPs are verified by external LLM before being silenced. Real findings are still fixed.
Same input grammar as the rest of the batch family.
You are the orchestrator
You — the model running THIS turn — drive the batch. You do NOT scan or fix anything yourself.
Step 0 — Resolve arguments
If no target was given, ask plain-text:
What should I full-scan-and-fix? Provide an absolute path, a GitHub URL, a marketplace, or a list file like @/tmp/plugins.txt.
Step 1 — Build the batch plan
# Separate the positional target specs from the --max-parallel flag in a
# single pass. We must NOT collapse to "$1": the shared batch input grammar
# lists a whitespace-separated LIST (`./a ./b ./c`) as a valid shape, and the
# orchestrator's `plan` subcommand declares its inputs as `nargs="+"`, so
# every positional must be forwarded — using only "$1" would silently
# scan-and-fix the first plugin and drop the rest, and would mis-bind a
# leading `--max-parallel` token as the input spec.
#
# Both --max-parallel N (two tokens) and --max-parallel=N (one token) are
# handled, because argparse accepts the `=` form and a user may type it.
# Without this loop the advertised `--max-parallel N` knob is silently
# ignored (MAX_PARALLEL stays at the default 8). Default 8; the orchestrator
# re-caps at 16, so a larger N is safe to pass.
BATCH_SPECS=()
MAX_PARALLEL=8
while [ "$#" -gt 0 ]; do
case "$1" in
--max-parallel)
MAX_PARALLEL="$2"
shift 2
;;
--max-parallel=*)
MAX_PARALLEL="${1#--max-parallel=}"
shift
;;
*)
BATCH_SPECS+=("$1")
shift
;;
esac
done
if [ "${#BATCH_SPECS[@]}" -eq 0 ]; then
echo "ERROR: no target spec given to /cpv-batch-full-scan-and-fix" >&2
exit 1
fi
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/cpv_batch_orchestrator.py" plan \
"${BATCH_SPECS[@]}" \
--agent cpv-plugin-fixer-agent \
--mode batch_same_turn_full \
--max-parallel "$MAX_PARALLEL"
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.
- 6d ago First seen · 240 lines · 109 tokens per session scan A 20f7034a02c9
cpv-batch-full-scan-and-fix is a command published in the GitHub repository Emasoft/claude-plugins-validation (4 stars, last pushed 2d ago), licensed MIT. It adds 109 tokens to every session and 2,323 once invoked, about $0.0005 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.