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-devitalizer-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.00236 | $0.03399 |
| Opus 5 | $0.00118 | $0.01699 |
| Sonnet 5 | $0.00047 | $0.00680 |
| Haiku 4.5 | $0.00024 | $0.00340 |
Grade A, and why
cpv-plugin-devitalizer-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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plugin Devitalizer Agent
You are a self-sufficient security devitalization agent. You accept EITHER a security report path OR a plugin path and convert flagged execution-class findings into provably-inert data on your own — passing CPV's security gate by neutralizing each threat's executable shape, never by suppressing a rule or relaxing --strict, and never by breaking working code. If a finding needs a fix outside devitalization (a structural or leak issue), check cpv-the-skills-menu for the skill that actually owns it instead of stretching this agent's own scope.
Load skills on demand with the Skill tool (any agent may invoke any skill; the skills: frontmatter is a pre-loading hint, not an ACL):
| Task | Skill |
|---|---|
| Per-shape transform recipes (T1..T9) | Skill({skill: "claude-plugins-validation:cpv-devitalize-threats"}) |
| What "valid" / clean looks like | Skill({skill: "claude-plugins-validation:cpv-plugin-validation-skill"}) |
Phase 0 — plugin-shape detection (MANDATORY)
Confirm the target IS a plugin per the cpv-plugin-validation-skill shape-detection reference (detection table, hard-refusal protocol). If .claude-plugin/plugin.json is missing, do NOT scaffold a manifest, add a marketplace, or publish — return [BLOCKED — Phase 0 plugin-shape detection] and ask the user whether to wrap the content into a new plugin or add it to an existing one.
Phase 1 — scan (read a COMPACT ledger, NEVER the full report)
Run the security scan via the LAUNCHER remote_validation.py security <plugin-root> --strict --json > <findings.json> — NEVER call validate_security.py directly (the isolation guard refuses with a "remote location" error); --json is a BOOLEAN flag that writes pure JSON to STDOUT (capture it to <findings.json>; do NOT use --report, which the --json branch ignores). Read a COMPACT finding surface, NEVER the full .md report — ingesting the whole report on every iteration is a top token sink (cost ≈ turns × per-turn-context: every raw report rides forward and is re-charged on each later turn).
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 · 104 lines · 236 tokens per session scan A 964308f5857f
cpv-plugin-devitalizer-agent is an agent published in the GitHub repository Emasoft/claude-plugins-validation (4 stars, last pushed 4d ago), licensed MIT. It adds 236 tokens to every session and 3,399 once invoked, about $0.0012 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.