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.
/plugin marketplace add Emasoft/claude-plugins-validation/plugin install 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-skill-validation-skill)<a href="https://agentmods.dev/skills/emasoft/claude-plugins-validation/cpv-skill-validation-skill"><img src="https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-skill-validation-skill/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-skill-validation-skill"><img src="https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-skill-validation-skill.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.00061 | $0.01202 |
| Opus 5.5 | $0.00024 | $0.00481 |
| Sonnet 5.5 | $0.00012 | $0.00240 |
| Haiku 4.5 | $0.00006 | $0.00120 |
Grade A, and why
cpv-skill-validation-skill 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.
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Validation Skill
Validates skill directories using 190+ validation rules from:
- AgentSkills OpenSpec — 44 rules
- Nixtla Quality Standards — 52 rules
- Meta-Skill Validation — 47 rules
- Component Validators — 25 rules
Overview
Script-based validation of structure, frontmatter, content, and pillars. For semantic analysis use /cpv-semantic-validation.
Prerequisites
- Python 3.12+ with
pyyamlinstalled - Skill directory containing a SKILL.md file
Instructions
- (
${CLAUDE_PLUGIN_ROOT}is set automatically by Claude Code at agent invocation — points at the locally-installed CPV plugin) - Run basic validation via the launcher (NEVER call
validate_skill_comprehensive.pydirectly from the cache — environment-isolation guard refuses):uv run --with pyyaml python "${CLAUDE_PLUGIN_ROOT}/scripts/remote_validation.py" skill path/to/skill/ --report $MAIN_ROOT/reports/validate_skill/$(date +%Y%m%d_%H%M%S%z)-<slug>.md - Optionally add mode flags:
--strict(Nixtla),--openspec(AgentSkills whitelist),--pillars(8+1 for lang-/convert-) - Review the compact summary output (full report saved to file via
--report) - Fix issues using
/cpv-fix-validation <report_path> - Re-run validation until exit code 0
Output
- Syntactic Score: 0-100 numeric with tier (PASS / CONDITIONAL_PASS / FAIL)
- Exit Code: 0 (pass), 1 (CRITICAL), 2 (MAJOR), 3 (MINOR), 4 (NIT)
- Report File:
$MAIN_ROOT/reports/validate_skill/<YYYYMMDD_HHMMSS±HHMM>-<slug>.mdat the main-repo root (first entry ofgit worktree list) — never a linked worktree. Per-component subfolder + local-time+GMT-offset timestamp mandatory. Bothreports/andreports_dev/gitignored.
For Semantic Quality Grading (A-F letter grades), use
/cpv-semantic-validationinstead.
ALWAYS use --report — never let verbose output consume context.
Error Handling
- "SKILL.md not found": Ensure path points to a skill directory, not a file
- "Malformed YAML": Fix frontmatter syntax (check
---delimiters, quotes, colons) - "Dir must match skill name": Rename directory or update
namefield
What ships with it
4 files 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.
- 1mo ago First seen · 87 lines · 61 tokens per session scan A 284b6c11cc4f
cpv-skill-validation-skill is a skill published in the GitHub repository Emasoft/claude-plugins-validation (4 stars, last pushed 3d ago), licensed MIT. It adds 61 tokens to every session and 1,202 once invoked, about $0.0002 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-09-03.
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…
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…
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…
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…
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…