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-add-component-to-plugin)<a href="https://agentmods.dev/skills/emasoft/claude-plugins-validation/cpv-add-component-to-plugin"><img src="https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-add-component-to-plugin.svg" alt="Measured on agentmods" 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.00062 | $0.01052 |
| Opus 5 | $0.00031 | $0.00526 |
| Sonnet 5 | $0.00012 | $0.00210 |
| Haiku 4.5 | $0.00006 | $0.00105 |
Grade A, and why
cpv-add-component-to-plugin 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 6d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cpv-add-component-to-plugin
Overview
Adds a new component (skill / agent / command / hook / mcp) to an existing plugin without re-running the generator or hand-editing scaffolds. Each component lands as a minimal but valid stub with frontmatter that passes validate_plugin / validate_skill out of the box. Loaded dynamically via cpv-the-skills-menu, reached via the Manage → Add component menu branch.
Prerequisites
uvon PATH- Target plugin path with a valid
.claude-plugin/plugin.json - Component type known:
skill,agent,command,hook,mcp
Instructions
- Choose a component type (skill, agent, command, hook, mcp).
- Run the relevant invocation from "Examples" with the target plugin path + name + description.
- For
hook/mcp, verify the JSON file already exists or will be created (the script merges entries idempotently). - After scaffolding, refresh the README via the
cpv-refresh-readmeskill so the<!-- BEGIN AUTO-COMPONENTS -->block picks up the new component. - Re-validate the parent plugin via
cpv-plugin-validation-skillto confirm no drift was introduced.
Copy this checklist and track your progress:
- Component type chosen
-
add_component.pyinvoked with all required args - README refreshed via
refresh_readme.py -
validate_plugin --strictre-run - Exit 0 confirmed
Output
- A new file or merged JSON entry under the plugin's canonical component directory:
skill→skills/<name>/SKILL.mdagent→agents/<name>.mdcommand→commands/<name>.mdhook→hooks/hooks.json(merged)mcp→.mcp.json(merged)
- Idempotent: re-runs with the same args are no-ops.
Error Handling
| Error | Resolution |
|---|---|
existing file would be overwritten |
Re-run with --force only if you genuinely intend to clobber |
unknown --type |
Use one of: skill, agent, command, hook, mcp |
target is not a plugin |
Confirm .claude-plugin/plugin.json exists at the path |
hook event invalid |
See the canonical event list in CC docs (PreToolUse, PostToolUse, etc.) |
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.
- 6d ago First seen · 94 lines · 62 tokens per session scan A cfbc1560154b
cpv-add-component-to-plugin is a skill published in the GitHub repository Emasoft/claude-plugins-validation (4 stars, last pushed yesterday), licensed MIT. It adds 62 tokens to every session and 1,052 once invoked, about $0.0003 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…
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…