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-scope-fix)<a href="https://agentmods.dev/commands/emasoft/claude-plugins-validation/cpv-batch-scope-fix"><img src="https://agentmods.dev/badge/commands/emasoft/claude-plugins-validation/cpv-batch-scope-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-scope-fix"><img src="https://agentmods.dev/badge/commands/emasoft/claude-plugins-validation/cpv-batch-scope-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.00074 | $0.01605 |
| Opus 5.5 | $0.00030 | $0.00642 |
| Sonnet 5.5 | $0.00015 | $0.00321 |
| Haiku 4.5 | $0.00007 | $0.00161 |
Grade A, and why
cpv-batch-scope-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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/cpv-batch-scope-fix — Apply scope-aware doctor fixes across a fleet
Counterpart to /cpv-batch-scope-diagnose. After the doctor has
diagnosed each project, this command dispatches one per project in
fix mode to apply the obvious mechanical fixes the diagnostic
flagged. The same scope semantics apply (user / project /
local / full).
Per TRDD-a175f78d §3:
- NIT findings (duplicates with identical content) → auto-applied silently.
- CRITICAL findings (misplaced settings.local.json entries) → auto-applied silently.
- MAJOR / MINOR findings (content-differing duplicates,
untracked refs, etc.) → reported with a fix recipe but require
explicit user approval before applying. The same-turn variant
(
/cpv-batch-scope-diagnose-and-fix) handles MAJOR/MINOR inline; this command requires a prior diagnose pass.
LOCAL paths only — URL inputs are CRITICAL errors (the doctor
needs ~/.claude/ filesystem access).
You are the orchestrator
You — the model running THIS turn — drive the batch. You do NOT fix anything yourself.
Step 0 — Resolve arguments
If any input looks URL-shaped, surface the canonical CRITICAL
message (see /cpv-batch-scope-diagnose Step 0) and stop.
If no project list was given, default to $PWD.
Step 1 — Build the batch plan
BATCH_SPEC="${1:-$PWD}"
SCOPE="full"
MAX_PARALLEL=8
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/cpv_batch_orchestrator.py" plan \
"$BATCH_SPEC" \
--agent cpv-doctor-agent \
--mode batch_scope_fix \
--no-url \
--max-parallel "$MAX_PARALLEL"
Capture the orchestrator's stdout (PLAN, STATUS_TABLE,
SESSION_DIR, PLUGIN_COUNT, DISPATCH_GROUPS). $SESSION_DIR
is required by Steps 3 and 4 (emit-status "$SESSION_DIR/plan.json"),
so you MUST bind it here from the SESSION_DIR: line. Queue the
initial status table for the claude-menu-system Stop hook (emitted
post-turn via systemMessage — zero token cost, NEVER printed
inline by the orchestrator):
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 · 171 lines · 74 tokens per session scan A 4f9eae326f4d
cpv-batch-scope-fix is a command published in the GitHub repository Emasoft/claude-plugins-validation (4 stars, last pushed 3d ago), licensed MIT. It adds 74 tokens to every session and 1,605 once invoked, about $0.0003 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.