What is cpv-create-plugin?

A scaffolding tool for creating Claude Code plugin or marketplace repositories. It generates the standard repository files, automated checks, Git hooks, and publishing workflow.

Use it when creating a new plugin repository or marketplace repository that will be managed and published with Git and GitHub.

Starting a plugin repository from scratch means setting up many files and release steps correctly. This tool provides that initial structure for a plugin, a marketplace hub, or a repository serving both roles.

cpv-create-plugin — Skill by Emasoft

Install

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.

agentmods

npx agentmods add skills/emasoft/claude-plugins-validation/cpv-create-plugin

Any agent

npx skills add Emasoft/claude-plugins-validation --skill cpv-create-plugin

Clone the repo

git clone --depth 1 https://github.com/Emasoft/claude-plugins-validation

Made for: Claude Code, Codex.

Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,443 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00031	$0.01443
Opus 5	$0.00015	$0.00722
Sonnet 5	$0.00006	$0.00289
Haiku 4.5	$0.00003	$0.00144

Measured 2d ago against content hash d3441883f44b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

skills/cpv-create-plugin/SKILL.md · 111 lines

How it starts

The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Create Plugin / Marketplace

Overview

Scaffolds complete Claude Code plugin or marketplace repositories with standard files, CI/CD workflows, git hooks, and release pipeline.

Marketplace layout

CPV supports three layouts: A (hub-and-spoke), B (nested), C (marketplace-in-plugin, self-referential). Default to A for multi-plugin sets; suggest C when one repo should be both plugin and marketplace. See marketplace-layouts.md.

Prerequisites

git, uv, gh CLI on PATH
CPV plugin installed
GitHub account (for publishing)

Instructions

Create a Plugin Repository:

uv run "${CLAUDE_PLUGIN_ROOT}/scripts/generate_plugin_repo.py" <target-dir> \
  --name <plugin-name> --description "<description>" \
  --author "<author>" --author-email "<email>" \
  --github-owner <github-username> [--marketplace <name>]

Create a Marketplace Hub (HUBS ONLY — no plugin code inside):

uv run "${CLAUDE_PLUGIN_ROOT}/scripts/generate_marketplace_repo.py" <target-dir> \
  --name <marketplace-name> --owner-name "<display-name>" \
  --description "<description>" --github-owner <github-username>

After generation:
- Validate via launcher (alias plugin) — see references/launcher-invocation.md. Direct invocation refused.
  
  The one-liner · Why the launcher is mandatory · Direct invocation (development only)
- Fix ALL issues (CRITICAL, MAJOR, MINOR, NIT) — only WARNINGs may remain
- Init git: cd <target-dir> && git init && git add <the scaffolded paths> && git commit -m "Initial scaffold" (stage by name — a scaffold dir often already holds local scratch, and -A sweeps it into the first commit)
- Create repo: gh repo create <owner>/<name> --public --source . --push
- Configure hooks: git config core.hooksPath git-hooks

Copy this checklist and track your progress:

Repository generated
Validation passed
All issues fixed
Git initialized and committed
GitHub repo created
Hooks configured

Read the full file on GitHub · 111 lines

Files

What ships with it

6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

2d ago First seen · 111 lines · 31 tokens per session scan A d3441883f44b

Subscribe to this mod's changes

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

Building agents

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 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