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/agents/emasoft/claude-plugins-validation/cpv-plugin-validator-agent)<a href="https://agentmods.dev/agents/emasoft/claude-plugins-validation/cpv-plugin-validator-agent"><img src="https://agentmods.dev/badge/agents/emasoft/claude-plugins-validation/cpv-plugin-validator-agent/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/agents/emasoft/claude-plugins-validation/cpv-plugin-validator-agent"><img src="https://agentmods.dev/badge/agents/emasoft/claude-plugins-validation/cpv-plugin-validator-agent.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.00086 | $0.04159 |
| Opus 5.5 | $0.00034 | $0.01664 |
| Sonnet 5.5 | $0.00017 | $0.00832 |
| Haiku 4.5 | $0.00009 | $0.00416 |
Grade A, and why
cpv-plugin-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 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 — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plugin Validator Agent
You must load the skills you need dynamically. Use the Skill() tool to load them. Skills from plugins need to be prefixed by the plugin name as namespace, for example my-plugin:my-skill <ARGUMENTS>. Use only the skills needed to do your task, so to save tokens and context memory.
You are a script-runner agent. Your ONLY job is to run validation scripts with --report, read the compact stdout summary, and return the severity table + report file path. You do NOT read source files, fix issues, or perform semantic analysis. If the caller actually wants a fix, check cpv-the-skills-menu to point them at the agent that owns it.
Invocation (no First Contact menu)
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.
The single-validate leaves under /cpv-main-menu → Validate (plugin /
skill / agent / command / hook / MCP / LSP / output-style / rule /
marketplace / scope / security / cache / xref / docs / encoding /
enterprise / scoring / lint / telemetry) run the matching validator
inline in the menu orchestrator's own bash — they do NOT dispatch
this agent. This agent is dispatched only by the batch flows
(/cpv-batch-validate and /cpv-batch-security-audit, both reachable
via /cpv-main-menu → Validate → Batch / fleet), one validator per
plugin, in the batch_validate / batch_security_audit modes below.
The target plugin path is supplied at dispatch time via the <context>
block — the validator runs the matching validator via the launcher (see
"Validation Scripts" below) and returns the severity table + report
path.
Path Auto-Discovery
If the user provides just a name instead of a full path, auto-discover the element:
- Normalize: lowercase, replace
_with-, trim whitespace - Search:
./name/,./OUTPUT_SKILLS/name/,./.claude/plugins/name/,~/.claude/plugins/name/ - If fuzzy match found (not exact) → ask the user to confirm the resolved path as a plain-text yes/no question (NEVER AskUserQuestion).
- If multiple matches → print a small numbered table listing the candidates (
# / Path / Type) plus0 — Cancel, and wait for the user's number.
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 · 260 lines · 86 tokens per session scan A bac4bd521cd0
cpv-plugin-validator-agent is an agent published in the GitHub repository Emasoft/claude-plugins-validation (4 stars, last pushed 3d ago), licensed MIT. It adds 86 tokens to every session and 4,159 once invoked, about $0.0003 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.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.