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/skills/emasoft/claude-plugins-validation/cpv-register-mcp)<a href="https://agentmods.dev/skills/emasoft/claude-plugins-validation/cpv-register-mcp"><img src="https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-register-mcp/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/skills/emasoft/claude-plugins-validation/cpv-register-mcp"><img src="https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-register-mcp.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.00067 | $0.01414 |
| Opus 5.5 | $0.00027 | $0.00566 |
| Sonnet 5.5 | $0.00013 | $0.00283 |
| Haiku 4.5 | $0.00007 | $0.00141 |
Grade A, and why
cpv-register-mcp 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cpv-register-mcp
Policy note (owner, 2026-08-19): MCP is supported but strongly discouraged for plugin integrations — prefer a CLI or script the agent invokes directly. Register an MCP server only when the target service runs exclusively over MCP. This skill stays fully functional (the option is never cut off — plugins, agent
mcpServers, or user-scoped settings all remain valid homes);validate_mcpemits a non-blocking INFO advisory when a plugin ships MCP.
Overview
Registers a new MCP server in a plugin's .mcp.json. The default transport is stdio (executable spawned per session). HTTP transport is also supported via the --http-url flag. The server's command MUST be cross-platform — invoke it via node, python3, uv run, or npx so it runs identically on Linux, macOS, and Windows. A bare relative shell-script command (e.g. ./run.sh) is a portability footgun: validate_mcp flags a relative file path that omits ${CLAUDE_PLUGIN_ROOT} as a MINOR finding, and a .sh entry point will not run on Windows at all — always wrap it in a cross-platform interpreter. Loaded dynamically via cpv-the-skills-menu, reached via the Create → Add MCP server menu branch.
Prerequisites
uvon PATH- Target plugin path with
.claude-plugin/plugin.json - A cross-platform command string (Python, Node, or
uv rundelegation) - Optional bundled executables under
servers/<server-name>/(v2.65.0+ convention)
Instructions
- Choose a unique server name within the plugin. Check
validate_mcpfor cross-source collisions (.mcp.json+ inlineplugin.json::mcpServersshadowing is a silent drop). - Reject the reserved server name
workspace(Claude Code v2.1.128+). - Write the command as a cross-platform invocation — never a bare shell script path.
- Bundled executables should live in
servers/<server-name>/per the canonical convention. - Run
add_component.py --type mcpwith the plugin path and server details. - Re-validate via
cpv-plugin-validation-skillandvalidate_mcp --strict.
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 · 99 lines · 67 tokens per session scan A 7de3baeb5f25
cpv-register-mcp is a skill published in the GitHub repository Emasoft/claude-plugins-validation (4 stars, last pushed 3d ago), licensed MIT. It adds 67 tokens to every session and 1,414 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…