agentmods.dev

cpv-batch-scope-fix

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

A batch tool that applies configuration fixes across multiple local project folders. It automatically makes only the defined safe changes and prepares other fixes for your approval.

In plain words
What is it for?
Use it after checking several projects to apply safe configuration corrections at user, project, local, or full scope. It changes files in place.
Why use it?
It removes the need to edit repeated configuration problems by hand across many projects. A prior diagnosis helps you see what will be changed.

Skill for Claude Code

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

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

not rated 4repo 3d ago A scan 100 tokens original MIT

Good fit Use it after checking several projects to apply safe configuration corrections at user, project, local, or full scope. It changes files in place.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/emasoft/claude-plugins-validation/cpv-batch-scope-fix
View source ↗ Emasoft/claude-plugins-validation
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-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-fix

README.md
[![agentmods](https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-batch-scope-fix/github.svg)](https://agentmods.dev/skills/emasoft/claude-plugins-validation/cpv-batch-scope-fix)
Your own site
<a href="https://agentmods.dev/skills/emasoft/claude-plugins-validation/cpv-batch-scope-fix"><img src="https://agentmods.dev/badge/skills/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.

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/emasoft/claude-plugins-validation/cpv-batch-scope-fix"><img src="https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-batch-scope-fix.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 100 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,070 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.00100 $0.01070
Opus 5.5 $0.00040 $0.00428
Sonnet 5.5 $0.00020 $0.00214
Haiku 4.5 $0.00010 $0.00107

Measured 1mo ago against content hash 1e8f2e2a6888, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

skills/cpv-batch-scope-fix/SKILL.md · 106 lines

How it starts

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

cpv-batch-scope-fix

Overview

Counterpart to cpv-batch-scope-diagnose. After the doctor has diagnosed each project, this skill dispatches one per project in fix mode to apply the obvious mechanical fixes. The same scope semantics apply.

Per TRDD-a175f78d §3:

  • NIT (duplicate-no-effect) → auto-applied silently.
  • CRITICAL (misplaced settings.local.json entry) → auto-applied.
  • MAJOR / MINOR → reported with a fix recipe in pending_fixes[]; user approves before applying.

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

Prerequisites

  • claude-plugins-validation plugin installed.
  • LOCAL filesystem access (same constraint as cpv-batch-scope-diagnose).
  • Write access to ~/.claude/ and <project>/.claude/ — this skill MUTATES filesystem state in place.
  • A prior diagnose pass is recommended (use cpv-batch-scope-diagnose first) so the user knows what will be touched.

Inputs

See the cpv-batch-scope-diagnose input table — every shape is supported identically. URL inputs are rejected.

Instructions

  1. Confirm the user wants APPLY-FIXES (this skill mutates ~/.claude/ and <project>/.claude/).
  2. Invoke the slash command body: 
    /cpv-batch-scope-fix <project-list> --scope <full|user|project|local>
  3. Each per-project agent runs in batch_scope_fix mode and writes the per-project status JSON.
  4. The user gets the final status table + a one-line summary + any pending_fixes for the unsafe MAJOR / MINOR recipes.
  5. For pending fixes, suggest running /cpv-batch-scope-diagnose-and-fix for the same-turn variant OR the doctor's per-project interactive flow (dispatch the cpv-doctor-agent on that single project; the non-interactive one-shot equivalent is the cpv-doctor CLI run from inside that project folder — it scopes to the active CLAUDE_PROJECT_DIR and takes no positional project-path argument).

Read the full file on GitHub · 106 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. 1mo ago First seen · 106 lines · 100 tokens per session scan A 1e8f2e2a6888

Subscribe to this mod's changes

cpv-batch-scope-fix is a skill published in the GitHub repository Emasoft/claude-plugins-validation (4 stars, last pushed 3d ago), licensed MIT. It adds 100 tokens to every session and 1,070 once invoked, about $0.0004 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.

DevOps and cloud
Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…

vercel/next.js · 123 tokens