cpv-setup-plugin-repo

cpv-setup-plugin-repo is a skill for Claude Code from Emasoft/claude-plugins-validation. It costs 54 tokens per session (1,374 once invoked), scanned A, original, MIT.

A setup tool for creating and configuring a Claude Code plugin repository on GitHub, a platform for hosting Git repositories.

In plain words
What is it for?
Use it when starting a new plugin repository and connecting it to CI/CD and a marketplace.
Why use it?
It prepares the repository with standard files, automated checks, release workflows, hooks, and optional marketplace notification.

Skill for Claude Code

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

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

Good fit Use it when starting a new plugin repository and connecting it to CI/CD and a marketplace.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/emasoft/claude-plugins-validation/cpv-setup-plugin-repo
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.

Any agent
npx skills add Emasoft/claude-plugins-validation --skill cpv-setup-plugin-repo
Clone the repo
git clone --depth 1 https://github.com/Emasoft/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-setup-plugin-repo

README.md
[![agentmods](https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-setup-plugin-repo/github.svg)](https://agentmods.dev/skills/emasoft/claude-plugins-validation/cpv-setup-plugin-repo)
Your own site
<a href="https://agentmods.dev/skills/emasoft/claude-plugins-validation/cpv-setup-plugin-repo"><img src="https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-setup-plugin-repo/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-setup-plugin-repo

Your own site · 80×15
<a href="https://agentmods.dev/skills/emasoft/claude-plugins-validation/cpv-setup-plugin-repo"><img src="https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-setup-plugin-repo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,374 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.00054 $0.01374
Opus 5 $0.00027 $0.00687
Sonnet 5 $0.00011 $0.00275
Haiku 4.5 $0.00005 $0.00137

Measured 6d ago against content hash 324e38b0d660, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

cpv-setup-plugin-repo 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.

skills/cpv-setup-plugin-repo/SKILL.md · 91 lines

How it starts

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

Setup Plugin Repository

Overview

Creates a Claude Code plugin GitHub repo with CI/CD, git hooks, and marketplace notification.

Prerequisites

  • gh CLI authenticated, git, uv, and uvx on PATH
  • GitHub PAT with repo scope (optional, for marketplace)

Note: the CPV validator is fetched remotely from GitHub via uvx. Downstream plugins do NOT vendor scripts/validate_plugin.py — the canonical pipeline runs cpv-remote-validate plugin . --strict which pulls the current CPV release automatically.

Instructions

  1. Create GitHub repo: gh repo create <owner>/<name> --public --clone, then cd into it
  2. Initialize plugin: create standard files from plugin-repo-templates (see Resources)
  3. (Layout C only) Add self-marketplace: also create the marketplace manifest with a single self-entry, source "./". Both manifests share the same name and version.
  4. Install workflows: copy ci.yml and release.yml from plugin-workflows. Skip notify-marketplace.yml for Layout B/C (no separate marketplace repo).
  5. Install git hooks: uv run python scripts/publish.py --install-hook
  6. Configure marketplace (Layout A only): uv run python scripts/set_marketplace_pat.py <owner>/<repo>. Skip for B/C.
  7. Validate: uvx --from git+https://github.com/Emasoft/claude-plugins-validation --with pyyaml cpv-remote-validate plugin . --strict. Layout C also runs validate_marketplace.py --strict for name/version sync.
  8. Commit and push: stage, commit "Initial plugin scaffold", push to main

Copy this checklist and track your progress:

  • Create GitHub repo
  • Initialize plugin structure
  • (Layout C) Add self-marketplace manifest
  • Install CI/CD workflows (skip notify-marketplace.yml for B/C)
  • Install git hooks
  • Configure marketplace notification (Layout A only)
  • Validate (plugin + marketplace for Layout C)
  • Commit and push

Output

Report: repo URL, VALID/INVALID + severity counts, installed workflows/hooks, skipped steps.

Read the full file on GitHub · 91 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.

  1. 6d ago First seen · 91 lines · 54 tokens per session scan A 324e38b0d660

Subscribe to this mod's changes

cpv-setup-plugin-repo is a skill published in the GitHub repository Emasoft/claude-plugins-validation (4 stars, last pushed 3d ago), licensed MIT. It adds 54 tokens to every session and 1,374 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-09-03.

Related

Other skills, from other repositories

gh-bootstrap

Initialize GitHub repository configuration from vetted upstream templates. Use when setting up repository automation, issue and PR templates, CI workflows, or baseline GitHub project files for a new or existing repo.

bahayonghang/my-ai-cli-toolkit · 41 tokens

gh-infra

Overview of gh-infra and command workflow (import, validate, plan, apply). Use when managing GitHub repository settings, labels, actions settings, rulesets, secrets, variables, or files declaratively via YAML manifests.

babarot/gh-infra · 49 tokens

release-engineering

Version, changelog, tag, and publish a release. Use when cutting a release, setting up automated publishing to npm/PyPI/crates.io/Maven/Homebrew, deciding whether a change is major/minor/patch, writing release notes, adopting conventional commits or changesets, planning a 1.0, or handling a bad release that needs to…

the-open-agent/oss-skills · 108 tokens

ship

Ship a change with Baron — open a draft PR, move the issue to inreview, trigger its CI pipeline, and notify the team, as ONE deterministic single-pane workflow across scm + issues + ci + notify. Use when the user says "ship it", "ship this change", or asks to PR + run CI + notify together.

loncadev/baron · 70 tokens

github-workflow-automation

Advanced GitHub Actions workflow automation with AI swarm coordination, intelligent CI/CD pipelines, and comprehensive repository management.

ruvnet/agentic-flow · 26 tokens

deploy-pipeline-runbook

Use when a release spans multiple systems or vendors, order of operations matters with rollback planned up front, or a failed step in one system could corrupt state in a downstream system.

yeaight7/agent-powerups · 41 tokens