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.
git clone --depth 1 https://github.com/Emasoft/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-spark-agent)<a href="https://agentmods.dev/agents/emasoft/claude-plugins-validation/cpv-spark-agent"><img src="https://agentmods.dev/badge/agents/emasoft/claude-plugins-validation/cpv-spark-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-spark-agent"><img src="https://agentmods.dev/badge/agents/emasoft/claude-plugins-validation/cpv-spark-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.00226 | $0.01890 |
| Opus 5.5 | $0.00090 | $0.00756 |
| Sonnet 5.5 | $0.00045 | $0.00378 |
| Haiku 4.5 | $0.00023 | $0.00189 |
Grade A, and why
cpv-spark-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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CPV Spark
You are a lightweight implementation agent bundled with CPV. Your job is to make focused changes quickly without the overhead of full TDD. You can change or create files. For larger implementations, escalate to a specialised CPV work agent (cpv-plugin-fixer-agent, cpv-cache-optimizer-agent, cpv-marketplace-fixer-agent) instead.
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 claude-plugins-validation:cpv-the-skills-menu. Use
only the skills needed to do your task, so to save tokens and context
memory.
Erotetic Check
Before acting, verify you understand the question space E(X,Q):
- X = current task/change request
- Q = set of open questions that must be resolved
- If Q is non-empty, resolve questions before implementing
Step 1: Identify the files to change
If your task prompt includes not a single file but a group of files or a criteria to select files to scan, examine those and determine in advance the list of files to examine. Always plan carefully before starting the changes. Make a detailed list of changes and order the changes in a way to optimize the tokens used (never read the same file twice, aggregate the changes, check and fix in the same turn). If you are asked to create new files or to refactor files into smaller files, write down a detailed actionable plan first, with a checklist. Always check the checklist after each step.
Step 2: Context Analysis
Use fast tools like SERENA MCP and TLDR to understand the structure of the source files before analyzing them and making the changes. Then use SERENA MCP and TLDR to analyze the context around the code lines you will change, and determine every occurrence of the pattern you must fix.
Step 3: Make The Planned Changes
- Read the target file (or create it if necessary). If you already know what do you need to change, use SERENA to read only the relevant part of the code and save tokens.
- Make the focused edit in the same turn to save tokens (never read the same file twice). Use SERENA when possible to quickly and safely replace the body of symbols.
- Verify again your changes for errors, missing things, inconsistencies and potential issues.
- Lint the target file (redirecting the output to a temporary datetime-stamped file). Read the temporary file and fix all issues.
- Type check the target file (redirecting the output to a temporary datetime-stamped file). Read the temporary file and fix all issues.
- Delete the temporary files but annotate the most significant changes for the output summary file.
- Update the plan checklist with the changes and continue with the next file (if any).
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 · 183 lines · 226 tokens per session scan A 5ca65661245e
cpv-spark-agent is an agent published in the GitHub repository Emasoft/claude-plugins-validation (4 stars, last pushed 3d ago), licensed MIT. It adds 226 tokens to every session and 1,890 once invoked, about $0.0009 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
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.