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 skills add Emasoft/claude-plugins-validation --skill cpv-batch-scope-diagnosegit clone --depth 1 https://github.com/Emasoft/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/skills/emasoft/claude-plugins-validation/cpv-batch-scope-diagnose)<a href="https://agentmods.dev/skills/emasoft/claude-plugins-validation/cpv-batch-scope-diagnose"><img src="https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-batch-scope-diagnose/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/skills/emasoft/claude-plugins-validation/cpv-batch-scope-diagnose"><img src="https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-batch-scope-diagnose.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.00114 | $0.01077 |
| Opus 5.5 | $0.00046 | $0.00431 |
| Sonnet 5.5 | $0.00023 | $0.00215 |
| Haiku 4.5 | $0.00011 | $0.00108 |
Grade B, and why
cpv-batch-scope-diagnose scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- `local`: `<project>/.claude/settings.local.json` How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cpv-batch-scope-diagnose
Overview
Read-only scope-aware doctor across a fleet of project folders.
Each cpv-doctor-agent subagent diagnoses one of:
user:~/.claude/project:<project>/.claude/(git-tracked entries)local:<project>/.claude/settings.local.jsonfull: all of the above + cross-scope conflict checker
The orchestrator body lives in this plugin's
commands/cpv-batch-scope-diagnose.md slash-command file.
Prerequisites
claude-plugins-validationplugin installed.- LOCAL filesystem access — the doctor reads
~/.claude/and<project>/.claude/. URL inputs cannot reach these and are rejected with a CRITICAL message. - A valid Claude installation at
~/.claude/foruserandfullscopes.
Inputs
| Shape | Example |
|---|---|
| Single project folder | the absolute path to the project root |
| List of project folders (CLI) | multiple whitespace-separated entries |
| List file | a path prefixed with @, e.g. an inputs list file |
| Default (no input) | $PWD |
| URL or owner/repo | REJECTED with CRITICAL message |
Instructions
- Confirm the user wants READ-ONLY diagnosis. If they want
fixes, route to
cpv-batch-scope-fixorcpv-batch-scope-diagnose-and-fix. - Invoke the slash command body:
/cpv-batch-scope-diagnose <project-list> --scope <full|user|project|local> - Each per-project agent runs in
batch_scope_diagnosemode. - The user gets the final status table + a one-line summary
(
DONE: projects=N clean=X findings=Y warning-only=Z. Conflicts total: C). - If findings or conflicts surface, suggest
/cpv-batch-scope-fix --scope <same scope> <same target>.
Output
- Unicode-bordered status table (one row per project).
- One-line DONE summary.
- Per-project scope-doctor reports under
$MAIN_ROOT/reports/scope-doctor/<ts±tz>-<project>.md. - Per-project status JSONs.
Token contract
Same as cpv-batch-validate — ~3-4K main-session tokens for a
17-project batch.
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 · 98 lines · 114 tokens per session scan B 39b8b9189d18
cpv-batch-scope-diagnose is a skill published in the GitHub repository Emasoft/claude-plugins-validation (4 stars, last pushed 3d ago), licensed MIT. It adds 114 tokens to every session and 1,077 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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…
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.
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…
deck-retro
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…