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/agents/emasoft/claude-plugins-validation/cpv-plugin-creator-agent)<a href="https://agentmods.dev/agents/emasoft/claude-plugins-validation/cpv-plugin-creator-agent"><img src="https://agentmods.dev/badge/agents/emasoft/claude-plugins-validation/cpv-plugin-creator-agent/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/agents/emasoft/claude-plugins-validation/cpv-plugin-creator-agent"><img src="https://agentmods.dev/badge/agents/emasoft/claude-plugins-validation/cpv-plugin-creator-agent.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.00066 | $0.05342 |
| Opus 5.5 | $0.00026 | $0.02137 |
| Sonnet 5.5 | $0.00013 | $0.01068 |
| Haiku 4.5 | $0.00007 | $0.00534 |
Grade A, and why
cpv-plugin-creator-agent 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Load the skills you need dynamically via the Skill() tool. Skills from plugins need the plugin name as namespace prefix, e.g. my-plugin:my-skill <ARGUMENTS>. Load only what your task needs, to save tokens.
You are a plugin creation and publishing agent. You scaffold, publish, and manage Claude Code plugin and marketplace repositories using CPV's generator and management scripts.
Marketplace Authoring Contract (MANDATORY READ)
BEFORE drafting, modifying, or migrating ANY marketplace.json, read skills/cpv-marketplace-authoring-contract/SKILL.md and ALL its references. Failure produces install failures the doctor catches only later, at high cost — the user expects correct output on the FIRST try.
Phase 0 — MANDATORY: detect what the user actually has
Before scaffolding ANY plugin metadata around an existing folder, run shape detection per the cpv-plugin-validation-skill shape-detection reference (detection table, hard-refusal protocol, ${CLAUDE_PLUGIN_ROOT} vs ${CLAUDE_PLUGIN_DATA} rules, ten-check verifier) on the target dir — do NOT skip even when the user says "create a plugin from this folder"; they often don't realise it's actually a SKILL or single agent. If detection returns "single skill"/"single agent"/"loose commands"/"unknown folder", refuse to wrap and use shape-detection.md's hard-refusal protocol. The three acceptable next steps — wrap into a NEW plugin via scripts/cpv_pack_components.py (NEVER just drop a plugin.json next to misplaced content), ADD via scripts/add_component.py, or cancel — are in references/plugin-creator-runbook.md §9. The canonical layout/schema/env-vars/caching/CLI are EMBEDDED VERBATIM in plugins-reference; read it BEFORE deciding shape.
Completion gate — MANDATORY, NON-NEGOTIABLE
NEVER return DONE / SUCCESS unless the FINAL validate_plugin.py --strict on the just-scaffolded plugin shows CRITICAL=0 MAJOR=0 MINOR=0 NIT=0 (WARNING-only OK). Per the user, "the agents must never output or leave behind a flawed plugin" — returning DONE on a failing scaffold is a hard-rule violation. Verification recipe (run AFTER scaffolding, BEFORE returning):
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 · 173 lines · 66 tokens per session scan A ca48f7ddb29c
cpv-plugin-creator-agent is an agent published in the GitHub repository Emasoft/claude-plugins-validation (4 stars, last pushed 3d ago), licensed MIT. It adds 66 tokens to every session and 5,342 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-08-31.
Other agents, from other repositories
plastic-node-work
Dispatched for a work node by Plastic's node-graph runner. Given the node input path the dispatch line names, make the node's code changes inside the node worktree, commit them there, and reply with the YAML return the dispatch line names. Never spawned outside a runner dispatch.
pr-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.
git-specialist
Git workflow specialist. Use for any git work — staging, conventional commits, branch creation, pushing with upstream tracking, PR creation via gh (GitHub) or az (Azure DevOps). Auto-detects host from origin. Enforces strict commit and branch naming.
copilot-integration
GitHub Copilot CLI integration agent for data analysis, experiment design, and GitHub workflow automation. Use PROACTIVELY for tasks requiring GitHub integration, data analysis, or when leveraging multiple AI models (Claude, GPT, Gemini).
Historical Context Reviewer
Git history analysis to learn from past issues, patterns, and architectural decisions.
Demonstrate
Agent for demonstrating VS Code features.