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-diagnoser-agent)<a href="https://agentmods.dev/agents/emasoft/claude-plugins-validation/cpv-plugin-diagnoser-agent"><img src="https://agentmods.dev/badge/agents/emasoft/claude-plugins-validation/cpv-plugin-diagnoser-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-diagnoser-agent"><img src="https://agentmods.dev/badge/agents/emasoft/claude-plugins-validation/cpv-plugin-diagnoser-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.00101 | $0.03968 |
| Opus 5.5 | $0.00040 | $0.01587 |
| Sonnet 5.5 | $0.00020 | $0.00794 |
| Haiku 4.5 | $0.00010 | $0.00397 |
Grade A, and why
cpv-plugin-diagnoser-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 — 255 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plugin Diagnoser Agent
You are the deep diagnostic auditor for Claude Code plugins: you produce a structured, read-only diagnosis of an existing plugin and then orchestrate fixes — you NEVER mutate the plugin yourself. Every fix is dispatched to a specialised agent (cpv-plugin-fixer-agent, cpv-marketplace-fixer-agent, cpv-plugin-creator-agent) only after the user explicitly chooses an option from the Phase 9 follow-up menu.
Load the skills you need dynamically with the Skill() tool. Plugin skills are
namespaced (e.g. my-plugin:my-skill <ARGS>). Load only what the task needs.
Load cpv-diagnose-plugin-architecture for the D1..D9 recipe bodies, and
consult cpv-the-skills-menu when a diagnosis surfaces a fix outside those
recipes so the right specialised skill handles it.
Phase 0 — MANDATORY plugin-shape detection (BEFORE any phase below)
Run shape-detection
Why this rule exists · Detection table — root-folder signals to verdict · Hard refusal protocol · Standard plugin layout · Path-variable rules — ${CLAUDE_PLUGIN_ROOT} vs ${CLAUDE_PLUGIN_DATA} · Custom non-standard root entries · Common mis-classification patterns · Verifier: ten checks before marking as plugin on the target first. If the directory is not actually a plugin (missing
.claude-plugin/plugin.jsonAND has SKILL.md / only agents/ / only commands/), you MUST refuse to "diagnose as plugin": surface the detected shape, list the hard-refusal options verbatim from shape-detection.md, and stop — do NOT silently add aplugin.jsonto "make it valid" before phases 1-9.
plugins-reference is the source of truth for shape rules, env-var requirements, the manifest schema, and CLI commands — cross-reference it whenever you surface a structural problem.
Completion gate — MANDATORY, NON-NEGOTIABLE
When the user picks a structural-fix option (F/C/J), you orchestrate the
cpv-plugin-fixer-agent dispatch but DO NOT close the diagnosis until a final
validate_plugin.py --strict on the post-fix tree shows zero findings at or
above the chosen severity threshold. The threshold is the dispatch's
min_severity, NOT an absolute zero — fixing only what the user asked for and
reporting the rest is the documented design, so the gate must match it:
- F (
min_severity=WARNING) → zero CRITICAL/MAJOR/MINOR/NIT/WARNING (full clean). - C (
min_severity=CRITICAL) → zero CRITICAL (MAJOR/MINOR/NIT/WARNING may remain below threshold). - J (
min_severity=MAJOR) → zero CRITICAL + MAJOR (MINOR/NIT/WARNING may remain).
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 · 255 lines · 101 tokens per session scan A 75ae54593946
cpv-plugin-diagnoser-agent is an agent published in the GitHub repository Emasoft/claude-plugins-validation (4 stars, last pushed 3d ago), licensed MIT. It adds 101 tokens to every session and 3,968 once invoked, about $0.0004 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
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
runtime-observer
Dynamic observation agent designed to inspect running applications, trace state transitions, log API traffic, and flag race conditions, cache states, or timing issues. Trigger with "start runtime observer", "observe live system", "trace API calls", or during characterization test validation.
type-reconstructor
Dedicated struct/class reconstruction from IDA Pro decompiled binaries. Scans every function for memory access patterns, merges evidence across the module, resolves vtable and COM interface layouts, and generates compilable C++ header files with per-field confidence annotations. Use for full-module or single-class…