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-setup-github-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-setup-github-marketplace)<a href="https://agentmods.dev/skills/emasoft/claude-plugins-validation/cpv-setup-github-marketplace"><img src="https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-setup-github-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-setup-github-marketplace"><img src="https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-setup-github-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.01119 |
| Opus 5 | $0.00019 | $0.00560 |
| Sonnet 5 | $0.00008 | $0.00224 |
| Haiku 4.5 | $0.00004 | $0.00112 |
Grade A, and why
cpv-setup-github-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 5d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup GitHub Marketplace
Overview
Automates creation of a GitHub-hosted Claude Code plugin marketplace. Handles CI/CD setup, batch plugin linking, and cross-marketplace migration.
Marketplace layout
Three layouts: A (hub-and-spoke, separate repos), B (nested monorepo, subdirs), C (marketplace-in-plugin, single repo with both manifests, source="./"). Suggest A for multi-plugin sets, C for single-plugin repos. Details: marketplace-layouts.md.
Prerequisites
- GitHub CLI (
gh) authenticated withrepo,workflow,admin:repo_hookscopes - CPV validator installed for pre-push validation hooks
Instructions
- Create the marketplace repo and initialize
marketplace.json - Install CI/CD workflow templates and sync scripts
- Link plugins by fetching metadata and installing notification workflows
- Validate with
uvx --from git+https://github.com/Emasoft/claude-plugins-validation --with pyyaml cpv-remote-validate marketplace . --strict(remote CPV — no vendoring, no drift)
Copy this checklist and track your progress:
- Create marketplace repo
- Install CI/CD workflows
- Link plugins
- Run validation
See Marketplace Setup Guide for detailed commands:
Overview · Prerequisites · Arguments · Phase 1: Create Marketplace Repository · Phase 2: Install Infrastructure · Phase 3: Link Plugin Repos · Phase 4: Plugin Management · Phase 5: Validate and Verify · Error Handling · Examples
Output
Marketplace repo with marketplace.json + CI/CD + sync scripts; notify-marketplace.yml on each linked plugin repo.
Error Handling
PAT needs repo+workflow. Dispatch missing: confirm notify-marketplace.yml on plugin default branch. Run validate_marketplace.py --verbose. Full troubleshooting: below.
Examples
Input: new marketplace → Output: creates repo, installs CI/CD, generates README.
Input: --link org/my-plugin → Output: fetches metadata, adds entry, installs notify-marketplace.yml.
What ships with it
11 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.
- references/local-to-github-migration.md 14 KB
- references/marketplace-architecture.md 17 KB
- references/marketplace-layouts.md 23 KB
- references/marketplace-real-configs.md 9.5 KB
- references/marketplace-setup-guide.md 18 KB
- references/orphan-plugin-onboarding.md 13 KB
- references/plugin-linking-guide.md 20 KB
- references/readme-template.md 12 KB
- references/script-templates.md 51 KB
- references/troubleshooting.md 12 KB
- references/workflow-templates.md 20 KB
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.
- 5d ago Changed 596ea1e1247a
- 8d ago First seen · 84 lines · 39 tokens per session scan A e34df6809943
cpv-setup-github-marketplace is a skill published in the GitHub repository Emasoft/claude-plugins-validation (4 stars, last pushed 6d ago), licensed MIT. It adds 39 tokens to every session and 1,119 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
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
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.
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
github-release-management
GitHub release orchestration — automated versioning, testing, deployment, and rollback. Use when cutting a release, tagging a version, drafting release notes, or coordinating a deploy/rollback workflow.
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.