cpv-batch-scope-diagnose-and-fix

cpv-batch-scope-diagnose-and-fix is a command for Claude Code from Emasoft/claude-plugins-validation. It costs 90 tokens per session (1,601 once invoked), scanned A, original, MIT.

A batch command that checks and fixes configuration across multiple local project folders in one pass. It examines global, project, and local settings, where local settings are usually ignored by version control.

In plain words
What is it for?
Use it for a same-turn configuration sweep across a fleet of projects. It finds duplicate, misplaced, conflicting, and other scope-related settings, then fixes only changes judged safe.
Why use it?
It avoids running a separate diagnosis and repair pass for every project. Safe changes can be applied immediately, while uncertain changes remain for review.

Command for Claude Code

Written for Claude Code: user-invocable in frontmatter.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the claude-plugins-validation plugin — 52 skills, 14 commands, 14 agents shipped together

Good fit Use it for a same-turn configuration sweep across a fleet of projects. It finds duplicate, misplaced, conflicting, and other scope-related settings, then fixes only changes judged safe.

Compare 6 commands from other repositories ↓
Install

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.

Claude Code
/plugin marketplace add Emasoft/claude-plugins-validation
Claude Code
/plugin install claude-plugins-validation

Made for: Claude Code.

Or install claude-plugins-validation, the plugin that ships this one along with the rest of its 52 skills, 14 commands, 14 agents.

Wrote 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.

agentmods badge for cpv-batch-scope-diagnose-and-fix

README.md
[![agentmods](https://agentmods.dev/badge/commands/emasoft/claude-plugins-validation/cpv-batch-scope-diagnose-and-fix.svg)](https://agentmods.dev/commands/emasoft/claude-plugins-validation/cpv-batch-scope-diagnose-and-fix)
Your own site
<a href="https://agentmods.dev/commands/emasoft/claude-plugins-validation/cpv-batch-scope-diagnose-and-fix"><img src="https://agentmods.dev/badge/commands/emasoft/claude-plugins-validation/cpv-batch-scope-diagnose-and-fix.svg" alt="Measured on agentmods" height="20"></a>
Per session 90 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,601 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00090 $0.01601
Opus 5 $0.00045 $0.00800
Sonnet 5 $0.00018 $0.00320
Haiku 4.5 $0.00009 $0.00160

Measured 7d ago against content hash d7013f43b96a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

cpv-batch-scope-diagnose-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 7d 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.

commands/cpv-batch-scope-diagnose-and-fix.md · 173 lines

How it starts

The opening of the file, as written. The whole thing — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/cpv-batch-scope-diagnose-and-fix — Same-turn scope-aware sweep

Combines /cpv-batch-scope-diagnose and /cpv-batch-scope-fix into one per-project agent turn. Each cpv-doctor-agent reads each scope-anchored file ONCE, classifies findings, applies the obvious mechanical fixes inline, and writes the per-project status JSON.

Per TRDD-a175f78d §3, the same-turn variant auto-applies:

  • NIT (duplicate-no-effect) → silent
  • CRITICAL (misplaced local-scope entry) → silent
  • MAJOR / MINOR with a SAFE recipe (e.g. the fix is purely deleting a duplicate that has identical content modulo whitespace) → silent
  • MAJOR / MINOR with UNSAFE recipes (content-differing duplicates, untracked refs that the user might WANT preserved) → reported in pending_fixes[], not applied

LOCAL paths only — URL inputs are CRITICAL errors.

You are the orchestrator

You — the model running THIS turn — drive the batch. You do NOT diagnose or fix anything yourself.

Step 0 — Resolve arguments

URL inputs → canonical CRITICAL message (see /cpv-batch-scope-diagnose). Empty input → $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_same_turn \
  --no-url \
  --max-parallel "$MAX_PARALLEL"

Capture the orchestrator's stdout (PLAN, STATUS_TABLE, SESSION_DIR, PLUGIN_COUNT, DISPATCH_GROUPS) — Step 2 needs the plan to read plan.plugins / plan.session_dir, and Steps 3-4 need $SESSION_DIR/plan.json for emit-status. 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):

python3 "${CLAUDE_PLUGIN_ROOT}/scripts/print_menu.py" "$STATUS_TABLE"

NEVER print the menu inline; the CMS Stop hook emits via systemMessage at turn end.

Step 2 — Dispatch one doctor per project, same-turn

Read the full file on GitHub · 173 lines

Changes

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.

  1. 7d ago First seen · 173 lines · 90 tokens per session scan A d7013f43b96a

Subscribe to this mod's changes

cpv-batch-scope-diagnose-and-fix is a command published in the GitHub repository Emasoft/claude-plugins-validation (4 stars, last pushed yesterday), licensed MIT. It adds 90 tokens to every session and 1,601 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.