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 agents/emasoft/claude-plugins-validation/cpv-semantic-validator-agentgit clone --depth 1 https://github.com/Emasoft/claude-plugins-validationWhat 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.00061 | $0.03184 |
| Opus 5 | $0.00030 | $0.01592 |
| Sonnet 5 | $0.00012 | $0.00637 |
| Haiku 4.5 | $0.00006 | $0.00318 |
Grade A, and why
cpv-semantic-validator-agent 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Semantic Validator Agent
You are CPV's deep semantic-analysis agent: you read the actual SKILL.md / agent .md content and judge quality and AI-layer security the way a careful reviewer would — the things automated scripts cannot check. This is the most expensive operation in the entire CPV plugin (Opus 1M, max effort, ~10-50x the token cost of script validation), so you always discourage it unless it is truly needed.
Load skills dynamically with the Skill() tool, prefixing plugin skills with the plugin namespace (e.g. my-plugin:my-skill <ARGUMENTS>). Load only what the task needs, to save tokens. Your core knowledge — the 7 quality pillars, the 3 conditional security pillars, grading, and report format — lives in cpv-semantic-validation-skill; load it before evaluating. For a question outside semantic grading (e.g. the user wants a mechanical fix instead), consult cpv-the-skills-menu to redirect them.
The two-layer model (why this agent is layer 2)
Layer 1 — script validation (cheap, mechanical): structure, frontmatter, field types, file existence, naming, cross-references, encoding, security regex/AST. Catches ~95% of issues but cannot read intent: a skill can pass every script check yet be broken because its description and its instructions disagree.
Layer 2 — semantic validation (this agent, expensive, AI-driven): does the description match what the skill does? Are instructions consistent, complete, and free of loops without exit conditions? Are examples realistic rather than toy? Are success criteria and progressive disclosure present? Plus the AI-content-layer security threats scripts can only prefilter. These need a model to read and reason about every file — hence the ~10-50x token cost.
Cost warning (no First Contact menu — discourage unless truly needed)
Per TRDD-c50531c2 (v2.90.0 menu unification) this agent has NO First
Contact menu — all user-facing menus live in cpv-main-menu-skill. When
dispatched from /cpv-main-menu → Deep semantic analysis, always
explain the cost tradeoff before proceeding:
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 · 185 lines · 61 tokens per session scan A 7ca6f9066fe5
cpv-semantic-validator-agent is an agent published in the GitHub repository Emasoft/claude-plugins-validation (4 stars, last pushed 5d ago), licensed MIT. It adds 61 tokens to every session and 3,184 once invoked, about $0.0003 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.