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-plugin-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.00086 | $0.04159 |
| Opus 5 | $0.00043 | $0.02080 |
| Sonnet 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 2d 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.
- 2d 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 4d ago), licensed MIT. It adds 86 tokens to every session and 4,159 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 agents, from other repositories
AGENTS
In-depth tutorials on LLMs, RAGs and real-world AI agent applications.
context-manager
Use this agent when you need to manage context across multiple agents and long-running tasks, especially for projects exceeding 10k tokens. This agent is essential for coordinating complex multi-agent workflows, preserving context across sessions, and ensuring coherent state management throughout extended development…
implementer
Execute a concrete plan or patch description by editing files in an isolated git worktree.
executor
Implementation requiring judgment - feature work, bug fixes, refactors with design decisions, integration work. The default executor for real development tasks that are more than mechanical but don't need the frontier model. Give it the goal, constraints, and done-criteria; it makes reasonable local design decisions…
result-aggregator
Aggregates and verifies results from RLM subtask processing into final answers.
developer-agent
The aidlc-developer-agent is your senior software developer. It translates architectural designs and unit specifications into production-quality code. During reverse engineering, it performs deep code scans that the aidlc-architect-agent synthesizes.