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 agentmods add skills/emasoft/claude-plugins-validation/cpv-batch-validatenpx skills add Emasoft/claude-plugins-validation --skill cpv-batch-validategit 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-validate)<a href="https://agentmods.dev/skills/emasoft/claude-plugins-validation/cpv-batch-validate"><img src="https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-batch-validate.svg" alt="Measured on agentmods" 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 | $0.00085 | $0.01406 |
| Opus 5 | $0.00043 | $0.00703 |
| Sonnet 5 | $0.00017 | $0.00281 |
| Haiku 4.5 | $0.00009 | $0.00141 |
Grade A, and why
cpv-batch-validate 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 3d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cpv-batch-validate
Overview
Parallel-validation skill for a fleet of Claude Code plugins.
Resolves the user's input via scripts/cpv_marketplace_input.py
(every shape from §Inputs), builds a batch plan via
scripts/cpv_batch_orchestrator.py, dispatches one
cpv-plugin-validator-agent subagent per plugin in batch_validate mode,
and aggregates per-plugin status JSONs into a CMS-shaped
status_table spec which is queued via scripts/print_menu.py.
The claude-menu-system Stop hook emits the table to the user
post-turn (zero token cost — never enters the agent transcript).
The full orchestrator body lives in the plugin's
commands/cpv-batch-validate.md slash-command file. This SKILL.md
is the canonical entry point when the skill is invoked from
cpv-the-skills-menu (CPV agents) or from the /cpv-batch-validate
slash command directly.
Prerequisites
claude-plugins-validationplugin installed (providesscripts/cpv_marketplace_input.py,scripts/cpv_batch_orchestrator.py,scripts/print_menu.py(the claude-menu-system bridge), and thecpv-plugin-validator-agentagent).claude-menu-systemplugin installed (the Stop-hook menu emitter thatprint_menu.pyqueues specs for). Declared as a hard dependency in CPV'splugin.json;print_menu.pyfails fast with an install hint if missing.- For URL inputs:
giton PATH and network access togithub.comso the resolver cangit clone --depth 1each plugin/marketplace into${TMPDIR}/cpv-batch-input-<uuid>/. - For marketplace inputs: the marketplace must ship a parseable
.claude-plugin/marketplace.jsonat its root listing one or more plugins.
Inputs
| Shape | Example |
|---|---|
| Single plugin (local) | the absolute path of the plugin root |
| Single plugin (URL) | https://github.com/owner/plugin or owner/plugin |
| Single skill (local) | a folder whose root holds a SKILL-shaped file |
| Single skill (URL) | a github repo whose root is a skill |
| Skill pack (local) | a folder containing many skill subfolders (Anthropic-style ./skills/<name>/SKILL.md or flat ./<name>/SKILL.md) |
| Skill pack (URL) | a github repo containing many skill folders |
| Marketplace (local) | the absolute path of the marketplace root |
| Marketplace (URL) | https://github.com/owner/marketplace-repo |
| List (CLI) | multiple whitespace-separated entries |
| List (file) | a path prefixed with @, e.g. an inputs list file |
| Comma-separated | a single string of entries joined with commas |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 126 lines · 85 tokens per session scan A 1c612e576819
cpv-batch-validate is a skill published in the GitHub repository Emasoft/claude-plugins-validation (4 stars, last pushed yesterday), licensed MIT. It adds 85 tokens to every session and 1,406 once invoked, about $0.0004 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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.
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…