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 agentmods add commands/emasoft/claude-plugins-validation/cpv-batch-fixgit clone --depth 1 https://github.com/Emasoft/claude-plugins-validationWhat 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 | $0.00129 | $0.04956 |
| Opus 5 | $0.00064 | $0.02478 |
| Sonnet 5 | $0.00026 | $0.00991 |
| Haiku 4.5 | $0.00013 | $0.00496 |
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 2d 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 — 423 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/cpv-batch-fix — Parallel batch fix for large plugins
For plugins where the total set of findings can't comfortably fit
in a single cpv-plugin-fixer-agent agent's working context (and stay under
the ~50% utilisation level beyond which model quality begins to
degrade), the single-agent fix loop will silently exhaust its
context window mid-way and exit without finishing the job. The
"safe size" is per-model: bare opus / sonnet give 200K tokens
(~20-30 findings safe), the opus[1m] / sonnet[1m] variants
give 1M (~100-150 findings safe). Per the Anthropic subagent spec,
subagents cannot spawn other subagents, so cpv-plugin-fixer-agent
cannot parallelise itself.
This command does the parallelisation from the main session, which is the only place the Agent tool can fan out:
- Runs
scripts/cpv_batch_planner.pyto slice the findings into shards of ~30 (zero LLM cost). The planner uses scope-based grouping: every finding insideskills/<name>/belongs to theskills/<name>/scope (with refactor rights), every other finding belongs to a single-file scope. - Dispatches N
cpv-plugin-fixer-agentagents in a SINGLE main-session message, each given its own shard manifest. Each agent starts with a fresh context window (size determined bycpv-plugin-fixer-agent'smodel:frontmatter at dispatch time) and refactor rights insideskill_dirscopes — including the right to split an oversized SKILL.md into multiple smaller focused skills, externalise content intoreferences/*.md, etc. - Runs
scripts/cpv_batch_aggregator.pyonce the shards have all returned, producing one consolidated report (zero LLM cost). - Main-session token cost: ~3-4K total (just paths, no report bodies).
See TRDD-71e68ab5 (design/tasks/TRDD-20260519_114050+0200-71e68ab5-batch-fix-parallel-sharding.md)
for the full design.
You are the orchestrator
You — the model running THIS turn — orchestrate the slash command from
the main session. You do NOT do any fixing yourself. You delegate the
actual fix work to N parallel cpv-plugin-fixer-agent agents via the Agent tool,
each in batch_shard mode.
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.
- 2d ago First seen · 423 lines · 129 tokens per session scan A 07cfc91cecaf
cpv-batch-fix is a command published in the GitHub repository Emasoft/claude-plugins-validation (4 stars, last pushed 4d ago), licensed MIT. It adds 129 tokens to every session and 4,956 once invoked, about $0.0006 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
git
Git operations with intelligent commit messages and workflow optimization.
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.