Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Emasoft/claude-plugins-validationnpx agentmods add skills/emasoft/claude-plugins-validation/cpv-setup-marketplace-auto-notificationWrote 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-marketplace-auto-notification)<a href="https://agentmods.dev/skills/emasoft/claude-plugins-validation/cpv-setup-marketplace-auto-notification"><img src="https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-setup-marketplace-auto-notification/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-marketplace-auto-notification"><img src="https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-setup-marketplace-auto-notification.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.00059 | $0.01196 |
| Opus 5 | $0.00030 | $0.00598 |
| Sonnet 5 | $0.00012 | $0.00239 |
| Haiku 4.5 | $0.00006 | $0.00120 |
Grade A, and why
cpv-setup-marketplace-auto-notification 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.
How it starts
The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup Marketplace Auto Notification
Overview
Configures the plugin side of the auto-notify chain: plugin push → notify
workflow → repository_dispatch → marketplace receiver → marketplace.json
bump → Claude Code sees the new version on next refresh. Works for any
plugin/marketplace pair with placeholder substitution only.
Prerequisites
gh auth statusgreen for the owner of BOTH repos- PAT with
reposcope (or fine grained RW) — see pat-secret-setup.md - Marketplace has a
repository_dispatch: plugin-updatedreceiver (create from receiver-workflow-template.md) - Plugin has a valid
.claude-plugin/plugin.jsonwithname+version
Instructions
- Check env for
MARKETPLACE_PATfirst (length only — never print the value). If unset, walk the user through creating one and exporting it. - Set the secret via
scripts/set_marketplace_pat.py— never improvisegh secret set. Full rules and the forbidden-patterns list in pat-secret-setup.md.uv run python scripts/set_marketplace_pat.py <plugin> <marketplace> uv run python scripts/set_marketplace_pat.py --verify-only <plugin> <marketplace> - Install
notify-marketplace.ymlon the plugin repo from the template. - Verify the marketplace receiver exists on its default branch — create
it from
receiver-workflow-template.mdif missing. - Dry-run the chain without cutting a real release.
- Verify end-to-end: plugin run → marketplace run →
marketplace.jsonbumped → Claude Code refresh sees the new version.
Copy this checklist and track your progress:
- Check env for
MARKETPLACE_PAT - If absent, create PAT and export it
- Run
scripts/set_marketplace_pat.py(NEVER improvisegh secret set) - Verify secret exists via
--verify-only - Scaffold
notify-marketplace.yml - Verify marketplace receiver exists
- Dry-run end-to-end
What ships with it
4 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.
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.
- 6d ago First seen · 106 lines · 59 tokens per session scan A 3b8f1be39a15
cpv-setup-marketplace-auto-notification is a skill published in the GitHub repository Emasoft/claude-plugins-validation (4 stars, last pushed 3d ago), licensed MIT. It adds 59 tokens to every session and 1,196 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.
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.
emdash-github-actions
Sets up GitHub Actions CI/CD workflows for EmDash plugins — TypeScript type-checking, ESLint linting, Vitest testing, npm publishing, and automated releases. ALWAYS use this skill when a user wants to create, add, set up, or configure GitHub Actions, CI/CD, automated checks, or deployment workflows for an EmDash…
release-deploy
Release and deploy via GitHub tags and GitHub Actions (not every commit). Creates production releases from main and beta releases from staging using the GitHub CLI. Use when the user asks to release, ship, deploy, cut a version, tag a release, publish beta/production, create a GitHub Release, or bump a semver tag. On…
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
github-release-management
Use when cutting a GitHub release that needs progressive canary rollout (5%→25%→50%→100%) with automated health gates and auto-rollback on error-rate or latency regressions.
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.