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-the-skills-menu-creategit 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-the-skills-menu-create)<a href="https://agentmods.dev/skills/emasoft/claude-plugins-validation/cpv-the-skills-menu-create"><img src="https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-the-skills-menu-create/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-the-skills-menu-create"><img src="https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-the-skills-menu-create.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.00097 | $0.01230 |
| Opus 5.5 | $0.00039 | $0.00492 |
| Sonnet 5.5 | $0.00019 | $0.00246 |
| Haiku 4.5 | $0.00010 | $0.00123 |
Grade A, and why
cpv-the-skills-menu-create 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 1mo 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cpv-the-skills-menu-create — universal skill-discovery migrator
Overview
Convert any Claude Code plugin from static skills: frontmatter
preloads to cpv-the-skills-menu method. After this skill runs,
every agent in the target plugin has only cpv-the-skills-menu in
its preload list and picks operational skills dynamically via the
Skill() tool.
The canonical spec lives at the-skills-menu-spec — see the Resources section for the full heading list.
Prerequisites
- A Claude Code plugin repository (local path OR Git URL OR plugin name resolvable in the current workspace).
- Git available on
$PATH(for cloning remote targets). - Write access to the target plugin's filesystem.
Instructions
- Resolve the target plugin per the spec's §Target resolution — try in order: explicit Git URL, explicit local path, plugin-in-marketplace expression, bare plugin name search.
- Confirm plugin shape per §Plugin detection —
.claude-plugin/plugin.json+agents/+skills/. If ambiguous, ask the user. - Discover agents in
<plugin-root>/agents/*.md(must have YAML frontmatter). - Discover skills in
<plugin-root>/skills/*/SKILL.md. Note any standalone (user/local/project-scope) skills the plugin references. - Detect the plugin namespace from
.claude-plugin/plugin.jsonnamefield (fallback chain in §Plugin namespace detection). - Generate the catalog skill at
<plugin-root>/skills/cpv-the-skills-menu/SKILL.mdwith the frontmatter + body shape from §Generated frontmatter + §Generated content. Required sections:## Standalone Skills,## Plugin Skills. Do NOT listcpv-the-skills-menuinside its own catalog. - Rewrite every agent's frontmatter
skills:list to exactly[cpv-the-skills-menu]per §Agent frontmatter rewrite rule. Preserve every other field. - Insert the mandatory dynamic-loading instruction (§Agent body instruction rule) immediately after the frontmatter in every agent body.
- Run the Skill independence review (§Skill independence review). Flag any skill that assumes a specific named caller agent.
- Verify per §Verification checklist. Produce a diff summary.
- Report per §Final report.
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.
- 1mo ago First seen · 80 lines · 97 tokens per session scan A e864bdaa4285
cpv-the-skills-menu-create is a skill published in the GitHub repository Emasoft/claude-plugins-validation (4 stars, last pushed 3d ago), licensed MIT. It adds 97 tokens to every session and 1,230 once invoked, about $0.0004 per session on Opus 5.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
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…