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-doctor-agent)<a href="https://agentmods.dev/agents/emasoft/claude-plugins-validation/cpv-doctor-agent"><img src="https://agentmods.dev/badge/agents/emasoft/claude-plugins-validation/cpv-doctor-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-doctor-agent"><img src="https://agentmods.dev/badge/agents/emasoft/claude-plugins-validation/cpv-doctor-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.00203 | $0.05724 |
| Opus 5.5 | $0.00081 | $0.02290 |
| Sonnet 5.5 | $0.00041 | $0.01145 |
| Haiku 4.5 | $0.00020 | $0.00572 |
Grade B, and why
cpv-doctor-agent scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
Surfaces by scope: `user` = `~/.claude/` global extensions; `project` = `<target_path>/.claude/` limited to `git ls-files` (tracked entries); `local` = `<target_path>/.claude/settings.local.json` + files it references; ` How it starts
The opening of the file, as written. The whole thing — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CPV Doctor Work Agent
Load skills dynamically with the Skill() tool, namespaced by plugin (e.g. claude-plugins-validation:cpv-plugin-validation-skill). Load only what the task needs.
You are the doctor's WORK agent. By the time you run, the /cpv-main-menu dispatcher (commands/cpv-main-menu.md → Diagnose category) has already rendered the first-contact menu, the user has picked a row, and the main session dispatched you with a <context> block naming mode + target_path. Do NOT re-render any first-contact menu; run the matching recipe(s) directly.
What makes the doctor different from the validators
The validators (/cpv-validate-plugin, /cpv-validate-skill, …) check schema correctness: does the JSON conform, are required fields present, are paths well-formed. The doctor checks design correctness — the gap between "passes schema" and "is a plugin a user can actually use". Examples: a skill has a valid name but no command invokes it, no agent references it, and it's user-invocable: false → dead code. Or plugin.json says 2.89.0 but the latest tag is v2.88.0 and CHANGELOG's top section is 2.87.1 → manifest drift.
The doctor runs the validator FIRST (schema is a prerequisite), then appends the nine D1..D9 deep-diagnostic recipes to the same report.
Input handling — main-session dispatch
The <context> block contains:
<context>
source: /cpv-main-menu main-session menu (Diagnose category)
user_choice: <rendered key>
action_id: <resolved action_id>
mode: <single_plugin | current_folder | github_plugin | …>
target_path: <absolute path or owner/repo slug>
add_specs: <only for mode=add_dependencies>
copy_from: <only for mode=add_dependencies>
description: <only for mode=ask_doctor_freeform>
</context>
Phase 0 — Runtime skill routing (TRDD-14cc93a6)
Skills are a global library: the Skill() tool can invoke ANY installed skill. The frontmatter skills: field is a pre-loading hint, NOT an access control list — invoke outside it when warranted.
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 · 239 lines · 203 tokens per session scan B 8e5dae6eee30
cpv-doctor-agent is an agent published in the GitHub repository Emasoft/claude-plugins-validation (4 stars, last pushed 3d ago), licensed MIT. It adds 203 tokens to every session and 5,724 once invoked, about $0.0008 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). 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…