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.
npx skills add Emasoft/claude-plugins-validation --skill cpv-publish-to-marketplacegit clone --depth 1 https://github.com/Emasoft/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-publish-to-marketplace)<a href="https://agentmods.dev/skills/emasoft/claude-plugins-validation/cpv-publish-to-marketplace"><img src="https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-publish-to-marketplace/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-publish-to-marketplace"><img src="https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-publish-to-marketplace.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.00039 | $0.01219 |
| Opus 5 | $0.00019 | $0.00609 |
| Sonnet 5 | $0.00008 | $0.00244 |
| Haiku 4.5 | $0.00004 | $0.00122 |
Grade A, and why
cpv-publish-to-marketplace 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 8d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Publish Plugin to Marketplace
Overview
Publishes a validated Claude Code plugin to a GitHub-hosted marketplace repo. Configures notification workflow, PAT secret, and publish pipeline.
Handles all three CPV layouts:
- Layout A (separate plugin and marketplace repos) — full notify chain with
MARKETPLACE_PATand dispatch - Layout B (nested monorepo) — single repo, single tag, no cross-repo dispatch
- Layout C (marketplace-in-plugin self-referential) — single repo with both manifests, single tag, no cross-repo dispatch (skips Phase 1 entirely)
Prerequisites
- Plugin repo with valid plugin.json (name, version, description)
ghCLI authenticated (gh auth status)- For Layout A: marketplace repo with marketplace.json
- For Layout C: same repo also has marketplace.json with self-entry (
source: "./") uvon PATH, plugin haspyproject.toml
Instructions
Phase 0: Detect layout and discover marketplace
- Plugin root has marketplace.json → Layout C (skip Phase 1)
- Parent has marketplace.json → Layout B (skip Phase 1)
- Otherwise → Layout A: ask the user for
<owner>/<marketplace-repo>, verify withgh repo view.
Phase 1: Configure Notification Pipeline (Layout A only)
Skip for Layout B/C — both manifests live in the same repo.
- Create PAT: GitHub PAT with
reposcope (publish-pipeline-guide §1) - Set secret:
gh secret set MARKETPLACE_PAT --repo <owner>/<plugin-repo> --body "$MARKETPLACE_PAT"(MUST use--body) - Install notify-marketplace.yml: Copy from publish-pipeline-guide §2 →
.github/workflows/, fillMARKETPLACE_OWNER/MARKETPLACE_REPO - Verify CI:
ci.ymlconsolidated (lint + validate + test) percpv-canonical-pipeline
Phase 2: Configure Publish Pipeline
- Install publish.py:
test -f scripts/publish.py - Install pre-push hook:
uv run python scripts/publish.py --install-hook - Verify hooks:
git config core.hooksPathshowsgit-hooks
Phase 3: Publish
What ships with it
1 file 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.
- 8d ago First seen · 114 lines · 39 tokens per session scan A 19cb9fe76559
cpv-publish-to-marketplace is a skill published in the GitHub repository Emasoft/claude-plugins-validation (4 stars, last pushed 5d ago), licensed MIT. It adds 39 tokens to every session and 1,219 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-09-03.
Other skills, from other repositories
plugin-publish
A release guide for publishing Zhin.js plugins to npm, the JavaScript package registry, and to the Zhin plugin marketplace. It covers package metadata, versioning, release checks, and submission requirements.
flow-next-land
Autonomous PR babysitter tick. Fixes CI, resolves feedback, merges when converged, closes the spec, releases. Emits LANDVERDICT. Use when asked to land PRs.
last-tag
Show commits since the last tag in a formatted table. Use when user asks "what changed since last release", "commits since last tag", "last-tag", "what's new", or wants to see recent unreleased changes.
ship
Ship a build — pre-flight checks, deploy, document, verify, monitor. Use when deploying code, publishing packages, or releasing.
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.
taiyi-integration
A project workflow skill for closing a TaiyiForge change and recording it in a CHANGELOG.md file. It checks review results, tests, and the state of the working tree before archiving the change.