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-fix-marketplace-validationgit 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-fix-marketplace-validation)<a href="https://agentmods.dev/skills/emasoft/claude-plugins-validation/cpv-fix-marketplace-validation"><img src="https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-fix-marketplace-validation/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-fix-marketplace-validation"><img src="https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-fix-marketplace-validation.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.00074 | $0.01116 |
| Opus 5 | $0.00037 | $0.00558 |
| Sonnet 5 | $0.00015 | $0.00223 |
| Haiku 4.5 | $0.00007 | $0.00112 |
Grade A, and why
cpv-fix-marketplace-validation 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 10d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix Marketplace Validation — Error-to-Fix Index
Overview
Central lookup for the cpv-marketplace-fixer-agent agent. Given a marketplace validation error, find the reference file with fix instructions. During the current transition the canonical guides live in the shared skills/cpv-fix-validation/references/ directory — the Resources section below links to the README that records the current mapping.
This skill is scoped to mechanical per-error fixes. For architectural migration (converting a non-CPV marketplace to Layout A or Layout B), this skill is NOT the right tool — use cpv-migrate-marketplace-architecture instead.
Prerequisites
- A marketplace validation report from
validate_marketplace.pyorvalidate_marketplace_pipeline.py - Access to the shared fix guides listed in the Resources section below
Instructions
- Read the validation report for error messages with severity, file path, and optional
categorytag. - Screen for architecture findings first. If any finding has
category: architecture, stop and delegate tocpv-migrate-marketplace-architecture. Mechanical fixes cannot repair architectural issues. - For each remaining mechanical finding, consult
marketplace-error-index.md— the primary lookup covering bothvalidate_marketplace.py(structure, plugin entries, source types, submodules) andvalidate_marketplace_pipeline.py(publish.py, cliff.toml, CI workflow, tagging, secrets). - Jump from the index entry to the specific section in the detailed guide:
marketplace-fixes.md§1-4 — issues fromvalidate_marketplace.py(structure, entries, sources, submodules)marketplace-fixes.md§5-8 — issues fromvalidate_marketplace_pipeline.py(publish.py, cliff.toml, CI workflow, tags, secrets)
- Apply the fix using Edit following the guide's step-by-step instructions. Never improvise structural changes.
Copy this checklist and track your progress:
- Read validation report
- Screen for
category: architecture→ hand off if present - Match mechanical errors to fix guide sections
- Apply fixes in severity order (CRITICAL → MAJOR → MINOR → NIT)
- Re-run validation to confirm clean
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.
- 10d ago First seen · 78 lines · 74 tokens per session scan A 353c02da1d00
cpv-fix-marketplace-validation is a skill published in the GitHub repository Emasoft/claude-plugins-validation (4 stars, last pushed 3d ago), licensed MIT. It adds 74 tokens to every session and 1,116 once invoked, about $0.0004 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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
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…