agentmods.dev

cpv-canonical-pipeline

cpv-canonical-pipeline is a skill for Claude Code from Emasoft/claude-plugins-validation. It costs 61 tokens per session (2,156 once invoked), scanned A, original, MIT.

A standard for the files, automated checks, hooks, and release process used by Emasoft Claude Code plugin repositories. It adjusts the expected setup for different repository layouts and programming languages.

In plain words
What is it for?
Use it to create or audit plugin repository structure, continuous integration and delivery checks, hooks, and publishing files across supported layouts.
Why use it?
It gives you the right reference when creating or reviewing a plugin repository. This prevents comparing a project with the wrong standard and making harmful changes based on that comparison.

Skill for Claude Code

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

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 changed 3d ago A scan 61 tokens original MIT

Good fit Use it to create or audit plugin repository structure, continuous integration and delivery checks, hooks, and publishing files across supported layouts.

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-canonical-pipeline

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/emasoft/claude-plugins-validation/cpv-canonical-pipeline"><img src="https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-canonical-pipeline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 61 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,156 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.00061 $0.02156
Opus 5 $0.00030 $0.01078
Sonnet 5 $0.00012 $0.00431
Haiku 4.5 $0.00006 $0.00216

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

Security

Grade A, and why

cpv-canonical-pipeline 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 3d 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-canonical-pipeline/SKILL.md · 118 lines

How it starts

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

Canonical Plugin Pipeline Standard

Before you diff anything: determine the plugin's PROFILE. The pipeline comes in four profiles and the canon differs per profile, so a diff taken against the wrong one is meaningless — a legitimate 1400-line difference reads as catastrophic drift and invites a destructive "resync" that deletes working release machinery.

The canon for a plugin's publish.py is gen_publish_py() in scripts/generate_plugin_repo.py — generate it and diff against that. <cpv>/scripts/publish.py is CPV's own release pipeline and is NOT a template: it carries none of the per-plugin build gates, so diffing against it reports gates as "missing" that were never supposed to be there.

Overview

Defines the standard files, workflows, hooks, and release pipeline that every Emasoft Claude Code plugin repository MUST have. Covers Python, JavaScript/TypeScript, Rust, Go, and Shell plugins. Pipeline supports all three CPV layouts (A: separate plugin and marketplace repos; B: nested monorepo; C: marketplace-in-plugin self-referential single repo).

Profile-aware

The pipeline comes in four PROFILES, auto-detected from repo shape (or set authoritatively via the manifest cpv.pipeline_profile; detection fails safe to standard) by scripts/cpv_pipeline_profile.py's resolve_pipeline_profile(). The profile is a SELECTOR (which canon a file is compared against), never a SUPPRESSOR — every drift finding still fires:

  • standard — vendors the CPV validators and ships the standard gen_* workflows.
  • remote-validation — de-vendors the local validators; validation is ONLY the remote cpv-remote-validate --strict gate (its absence is the point).
  • submodule-build — build sources live in a git submodule, pre-built binaries are committed to bin/, and publish.py is submodule-aware.
  • binary-release — ships compiled binaries as RELEASE assets via a build matrix + stage script + CI smoke job + SHA256SUMS.

Layout C specifics

Read the full file on GitHub · 118 lines

Files

What ships with it

9 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. 3d ago Changed 1b0673f685bd
  2. 6d ago Changed fd8ba4d1bc38
  3. 10d ago First seen · 118 lines · 61 tokens per session scan A 392ff2e4103c

Subscribe to this mod's changes

cpv-canonical-pipeline is a skill published in the GitHub repository Emasoft/claude-plugins-validation (4 stars, last pushed 3d ago), licensed MIT. It adds 61 tokens to every session and 2,156 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-08-31.

CI and CDDevOps and cloudGit and workflowReleases
Related

Other skills, from other repositories

ship

Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. (gstack).

garrytan/gstack · 35 tokens

github-release-management

Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.

ruvnet/RuView · 27 tokens

gitlab-devops

GitLab DevOps operations — issues, merge requests, CI/CD pipelines, repository browsing, labels, milestones, releases, and wiki management. Use when querying GitLab project status, monitoring pipeline executions, browsing repository files, creating issues for network findings, opening merge requests for config…

automateyournetwork/netclaw · 67 tokens

seed-snapshot-release

An automated workflow for creating and tracking a snapshot release of the pull request on the current branch. A snapshot release is a temporary package build used for testing a branch before a normal release.

daangn/seed-design · 19 tokens

push-ci

Push to remote and monitor CI. Validates branch safety, executes git push WITH explicit user approval, then monitors CI run status via gh CLI. Use when: user says 'push', 'push and watch CI', 'ship it', 'push-ci'. Not for: committing (use /smart-commit), creating PRs (use /create-pr), merging (use /merge-prep).

sd0xdev/sd0x-harness · 82 tokens

release-engineering

Plan and verify software releases with versioning, changelogs, release branches, feature flags, canaries, migration gates, rollback, deployment checks, and release readiness. Use when preparing a release, shipping a risky PR, coordinating app/backend/database rollout, recovering from a bad deploy, or defining release…

majiayu000/spellbook · 69 tokens