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-create-plugin)<a href="https://agentmods.dev/skills/emasoft/claude-plugins-validation/cpv-create-plugin"><img src="https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-create-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.
<a href="https://agentmods.dev/skills/emasoft/claude-plugins-validation/cpv-create-plugin"><img src="https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-create-plugin.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.00031 | $0.01513 |
| Opus 5.5 | $0.00012 | $0.00605 |
| Sonnet 5.5 | $0.00006 | $0.00303 |
| Haiku 4.5 | $0.00003 | $0.00151 |
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 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 — 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,ghCLI 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-Asweeps it into the first commit) - Create repo:
gh repo create <owner>/<name> --public --source . --push - Configure hooks:
git config core.hooksPath git-hooks
- Validate via launcher (alias
Copy this checklist and track your progress:
- Repository generated
- Validation passed
- All issues fixed
- Git initialized and committed
- GitHub repo created
- Hooks configured
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.
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 Changed 909d9d9d26cc
- 1mo ago First seen · 111 lines · 31 tokens per session scan A d3441883f44b
cpv-create-plugin is a skill published in the GitHub repository Emasoft/claude-plugins-validation (4 stars, last pushed 3d ago), licensed MIT. It adds 31 tokens to every session and 1,513 once invoked, about $0.0001 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 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…