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.
/plugin marketplace add Emasoft/claude-plugins-validation/plugin install 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-link-plugin-marketplace)<a href="https://agentmods.dev/skills/emasoft/claude-plugins-validation/cpv-link-plugin-marketplace"><img src="https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-link-plugin-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-link-plugin-marketplace"><img src="https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-link-plugin-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.00052 | $0.00852 |
| Opus 5 | $0.00026 | $0.00426 |
| Sonnet 5 | $0.00010 | $0.00170 |
| Haiku 4.5 | $0.00005 | $0.00085 |
Grade A, and why
cpv-link-plugin-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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cpv-link-plugin-marketplace
Overview
Appends an existing plugin to an existing marketplace's marketplace.json, preserving entries for other plugins. If a plugin with the same name is already listed, its entry is replaced in place with fresh metadata (so re-runs stay idempotent — one entry per name, never duplicated). Uses the correct source.source schema key (not the legacy source.type). Loaded dynamically via cpv-the-skills-menu, reached via the GitHub setup → Link plugin menu branch.
Prerequisites
uvon PATH- A local marketplace directory containing
.claude-plugin/marketplace.json(ormarketplace.jsonat root) - A plugin to link, given as either:
- A local plugin directory path (will be converted to relative-to-marketplace source)
- A GitHub repo slug
owner/repo(emits{source: "github", repo: "owner/repo"})
Instructions
- Confirm the marketplace's
marketplace.jsonexists at the canonical location. - Choose the plugin source form: local path or
owner/repoGitHub slug. - Invoke
manage_plugin.py --link-plugin <marketplace-path> <plugin-spec>. - The script appends a new entry. Entries for other plugins are left untouched; an existing entry with the same
nameis replaced in place with fresh metadata. - Re-validate the marketplace via
cpv-plugin-validation-skill(orvalidate_marketplace.py --strict).
Copy this checklist and track your progress:
- Marketplace path confirmed valid
- Plugin spec form chosen (local path OR
owner/repo) -
manage_plugin.py --link-pluginexecuted -
marketplace.jsonupdated -
validate_marketplace.py --strictre-run, exit 0
Output
- A new entry appended to
marketplace.json::plugins[]. - For local plugins:
source: "relative-path"with relative path stored. - For GitHub plugins:
source: "github"withrepo: "owner/repo".
Error Handling
| Error | Resolution |
|---|---|
| Marketplace not found | Verify path; check for .claude-plugin/marketplace.json |
| Plugin already linked | Re-runs are idempotent — the same-name entry is replaced in place (refreshing version/description), never duplicated |
| Local plugin not found | Verify path; .claude-plugin/plugin.json must exist |
| GitHub repo invalid | Verify owner/repo slug exists on GitHub |
| Validator regression after link | Check upstream cross-validation (RC-MKPL-*) findings |
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 · 76 lines · 52 tokens per session scan A f6b2bc5736e0
cpv-link-plugin-marketplace is a skill published in the GitHub repository Emasoft/claude-plugins-validation (4 stars, last pushed 2d ago), licensed MIT. It adds 52 tokens to every session and 852 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…