agentmods.dev

cpv-add-component-to-plugin

cpv-add-component-to-plugin is a skill for Claude Code from Emasoft/claude-plugins-validation. It costs 62 tokens per session (1,052 once invoked), scanned A, original, MIT.

A scaffolding tool for adding a skill, agent, command, hook, or MCP component to an existing plugin. Scaffolding creates the initial valid files and structure for a new component.

In plain words
What is it for?
Use it when extending an existing plugin with one new component. Afterward, refresh the README and validate the plugin.
Why use it?
It avoids rebuilding the whole plugin or manually creating files that may fail validation. The new component starts as a minimal valid stub.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter. Also seen: mentions .claude-plugin.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the claude-plugins-validation plugin — 52 skills, 14 commands, 14 agents shipped together

not rated 4repo 3d ago A scan 62 tokens original MIT

Good fit Use it when extending an existing plugin with one new component. Afterward, refresh the README and validate the plugin.

Compare 6 skills from other repositories ↓
View source ↗ Emasoft/claude-plugins-validation
Install

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.

Claude Code
/plugin marketplace add Emasoft/claude-plugins-validation
Claude Code
/plugin install claude-plugins-validation

Made for: Claude Code.

Or install claude-plugins-validation, the plugin that ships this one along with the rest of its 52 skills, 14 commands, 14 agents.

Wrote 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.

agentmods badge for cpv-add-component-to-plugin

README.md
[![agentmods](https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-add-component-to-plugin/github.svg)](https://agentmods.dev/skills/emasoft/claude-plugins-validation/cpv-add-component-to-plugin)
Your own site
<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/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.

agentmods 80×15 button for cpv-add-component-to-plugin

Your own site · 80×15
<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="Reviewed on agentmods" width="80" height="20"></a>
Per session 62 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,052 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00062 $0.01052
Opus 5.5 $0.00025 $0.00421
Sonnet 5.5 $0.00012 $0.00210
Haiku 4.5 $0.00006 $0.00105

Measured 1mo ago against content hash cfbc1560154b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

skills/cpv-add-component-to-plugin/SKILL.md · 94 lines

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

  • uv on PATH
  • Target plugin path with a valid .claude-plugin/plugin.json
  • Component type known: skill, agent, command, hook, mcp

Instructions

  1. Choose a component type (skill, agent, command, hook, mcp).
  2. Run the relevant invocation from "Examples" with the target plugin path + name + description.
  3. For hook / mcp, verify the JSON file already exists or will be created (the script merges entries idempotently).
  4. After scaffolding, refresh the README via the cpv-refresh-readme skill so the <!-- BEGIN AUTO-COMPONENTS --> block picks up the new component.
  5. Re-validate the parent plugin via cpv-plugin-validation-skill to confirm no drift was introduced.

Copy this checklist and track your progress:

  • Component type chosen
  • add_component.py invoked with all required args
  • README refreshed via refresh_readme.py
  • validate_plugin --strict re-run
  • Exit 0 confirmed

Output

  • A new file or merged JSON entry under the plugin's canonical component directory:
    • skill → skills/<name>/SKILL.md
    • agent → agents/<name>.md
    • command → commands/<name>.md
    • hook → 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.)

Read the full file on GitHub · 94 lines

Changes

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.

  1. 1mo ago First seen · 94 lines · 62 tokens per session scan A cfbc1560154b

Subscribe to this mod's changes

cpv-add-component-to-plugin is a skill published in the GitHub repository Emasoft/claude-plugins-validation (4 stars, last pushed 3d ago), licensed MIT. It adds 62 tokens to every session and 1,052 once invoked, about $0.0002 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.

Building agents
Related

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens

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…

vercel/next.js · 123 tokens