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-migrate-marketplace-architecturegit 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-migrate-marketplace-architecture)<a href="https://agentmods.dev/skills/emasoft/claude-plugins-validation/cpv-migrate-marketplace-architecture"><img src="https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-migrate-marketplace-architecture/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-migrate-marketplace-architecture"><img src="https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-migrate-marketplace-architecture.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.00070 | $0.01142 |
| Opus 5 | $0.00035 | $0.00571 |
| Sonnet 5 | $0.00014 | $0.00228 |
| Haiku 4.5 | $0.00007 | $0.00114 |
Grade A, and why
cpv-migrate-marketplace-architecture 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 12d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migrate Marketplace Architecture
Overview
Converts a non-CPV marketplace into one of three CPV layouts: A (hub-and-spoke), B (nested single-repo), or C (marketplace-in-plugin self-referential). Preserves per-plugin git history and logs every decision.
Prerequisites
ghauthenticated (BLOCKER for Layout A);git>= 2.34 (for subtree split); clean working tree;uvon PATH
Instructions
Architectural migration with AskUserQuestion interaction. Loaded only on an architecture finding or explicit user request.
- Pre-migration audit — pre-migration-audit. Verdict must be READY.
- Interrogate — interrogation-playbook. Target layout is the first question.
- Execute:
- A — layout-a-migration
- B — layout-b-discipline
- C — layout-c-migration
- Wire auto-notification (A only) —
cpv-setup-marketplace-auto-notification. B and C tag atomically. - Verify with
validate_marketplace.py --strictandvalidate_plugin.py --strict. - Write the migration log.
Copy this checklist and track your progress:
- Pre-migration audit READY
- Interrogation answers recorded
- Target layout selected (A, B, or C)
- Layout migration executed
- Auto-notification wired for each new plugin repo (Layout A only — B and C tag atomically)
-
validate_marketplace.py --strictpasses - Every plugin validates
- Migration log written
Output
- A: N plugin repos + cleaned marketplace (github sources, tagged), each wired for auto-notify.
- B: same repo with
publish.py,cliff.toml, CI,CHANGELOG.md, atomic commit tagged. - C: same repo gains the second manifest with self-entry (
source: "./"), name+version aligned,publish.pybumps both atomically. - Migration log at
$MAIN_ROOT/reports/cpv-migrate-marketplace-architecture/<ts±tz>-<slug>.md
What ships with it
5 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.
- 12d ago First seen · 88 lines · 70 tokens per session scan A 39c40e2218a7
cpv-migrate-marketplace-architecture is a skill published in the GitHub repository Emasoft/claude-plugins-validation (4 stars, last pushed 5d ago), licensed MIT. It adds 70 tokens to every session and 1,142 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
product-pair
Suggest complementary products that pair well with a given item — side tables for sofas, task lights for desks, etc. Use when the user asks "what goes with" a product, wants coordinating pieces, or asks to complete a furniture grouping.
cs-channel-message
A channel-message writing tool for search ads, advertising, customer relationship messages, and app notifications. It uses the NCM sequence—Need, Channel, Moment, Message, and CTA—to adapt wording to where and when customers see it.
commerce-detail-page-copy
A writing tool for Korean e-commerce product detail pages. It can generate a full 13-section page, assess an existing page, or create two persona-based copy sets.
master-schedule
Initialize, validate, inspect, or import the current project's local FF&E product library. Use when a product workflow needs product-library.csv, when the user invokes /as:master-schedule, or when legacy master-schedule.json or canoa.json configuration is present.
product-image-processor
Download, resize, and remove backgrounds from product images at scale. Use when the user asks to "process product images", batch-download images from the schedule, strip backgrounds, or standardize product photos.
product-match
Find visually or functionally similar products from an image, name, or description. Use when the user asks to "find something like this", match a product from a photo, or source alternates to a given item.