cpv-batch-scope-diagnose-and-fix

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

A batch tool that checks and fixes configuration files across multiple project folders in one run. It applies safe changes immediately and lists changes that need approval.

In plain words
What is it for?
Use it to inspect several local projects for configuration problems and apply obvious safe corrections. It supports user, project, local, or full configuration scopes.
Why use it?
It avoids running a separate check and fix pass for every project, reducing repeated file reading and work. Unsafe changes remain under your control.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter. Also seen: reads .claude/ paths; mentions subagents.

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

Good fit Use it to inspect several local projects for configuration problems and apply obvious safe corrections. It supports user, project, local, or full configuration scopes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/emasoft/claude-plugins-validation/cpv-batch-scope-diagnose-and-fix
Install

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.

Any agent
npx skills add Emasoft/claude-plugins-validation --skill cpv-batch-scope-diagnose-and-fix
Clone the repo
git clone --depth 1 https://github.com/Emasoft/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/skills/emasoft/claude-plugins-validation/cpv-batch-scope-diagnose-and-fix/github.svg)](https://agentmods.dev/skills/emasoft/claude-plugins-validation/cpv-batch-scope-diagnose-and-fix)
Your own site
<a href="https://agentmods.dev/skills/emasoft/claude-plugins-validation/cpv-batch-scope-diagnose-and-fix"><img src="https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-batch-scope-diagnose-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.

agentmods 80×15 button for cpv-batch-scope-diagnose-and-fix

Your own site · 80×15
<a href="https://agentmods.dev/skills/emasoft/claude-plugins-validation/cpv-batch-scope-diagnose-and-fix"><img src="https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-batch-scope-diagnose-and-fix.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 128 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 882 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.00128 $0.00882
Opus 5 $0.00064 $0.00441
Sonnet 5 $0.00026 $0.00176
Haiku 4.5 $0.00013 $0.00088

Measured 9d ago against content hash 394af9b29cde, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, 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 9d 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.

skills/cpv-batch-scope-diagnose-and-fix/SKILL.md · 89 lines

How it starts

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

cpv-batch-scope-diagnose-and-fix

Overview

Same-turn variant of the scope-aware doctor batch family. Each cpv-doctor-agent subagent reads each scope-anchored file ONCE, classifies findings, and applies the obvious mechanical fixes inline. Cuts per-project token cost ~2× vs running cpv-batch-scope-diagnose + cpv-batch-scope-fix separately.

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 → silent.
  • MAJOR / MINOR with UNSAFE recipes → reported in pending_fixes[] for user approval.

The orchestrator body lives in this plugin's commands/cpv-batch-scope-diagnose-and-fix.md slash-command file.

Prerequisites

  • Same as cpv-batch-scope-fix — LOCAL filesystem access, write permission on ~/.claude/ and <project>/.claude/.
  • A valid Claude installation at ~/.claude/ for user / full scopes.

Inputs

See the cpv-batch-scope-diagnose input table.

Instructions

  1. Confirm the user wants the SAME-TURN variant (faster, narrower visibility). If they want a separate diagnose pass first, route to cpv-batch-scope-diagnose + cpv-batch-scope-fix.
  2. Invoke the slash command body:
    /cpv-batch-scope-diagnose-and-fix <project-list> --scope <full|user|project|local>
    
  3. Each per-project agent runs in batch_scope_same_turn mode.
  4. The user gets the final status table + a one-line summary + any pending_fixes.

Output

  • Unicode-bordered status table.
  • One-line DONE summary.
  • Per-project final scope-doctor reports under $MAIN_ROOT/reports/scope-doctor/<ts±tz>-<project>-same-turn.md.
  • Per-project status JSONs.

Token contract

Same-turn mode trades intermediate visibility for ~2× lower per-project token cost.

Error Handling

Same as cpv-batch-scope-fix.

Examples

User: clean-sweep .claude/ across all my projects
Assistant: /cpv-batch-scope-diagnose-and-fix /path/a /path/b /path/c --scope full

User: same for just my user-scope settings
Assistant: /cpv-batch-scope-diagnose-and-fix --scope user

Read the full file on GitHub · 89 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. 9d ago First seen · 89 lines · 128 tokens per session scan A 394af9b29cde

Subscribe to this mod's changes

cpv-batch-scope-diagnose-and-fix is a skill published in the GitHub repository Emasoft/claude-plugins-validation (4 stars, last pushed 2d ago), licensed MIT. It adds 128 tokens to every session and 882 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.

Related

Other skills, from other repositories

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

diagnose

Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.

emdash-cms/emdash · 43 tokens

repro-admin

Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.

emdash-cms/emdash · 48 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

byted-util-volcengine-detect-retry

An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.

bytedance/agentkit-samples · 101 tokens