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.
git 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/commands/emasoft/claude-plugins-validation/cpv-the-skills-menu-create)<a href="https://agentmods.dev/commands/emasoft/claude-plugins-validation/cpv-the-skills-menu-create"><img src="https://agentmods.dev/badge/commands/emasoft/claude-plugins-validation/cpv-the-skills-menu-create.svg" alt="Measured on agentmods" 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.00099 | $0.01307 |
| Opus 5 | $0.00049 | $0.00654 |
| Sonnet 5 | $0.00020 | $0.00261 |
| Haiku 4.5 | $0.00010 | $0.00131 |
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 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 — 105 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
Convert a Claude Code plugin from static skills: [...] frontmatter
preloads to cpv-the-skills-menu method. After the migration 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.
This command is plugin-agnostic — it migrates any Claude Code
plugin you point it at (a local path, a Git URL, a marketplace + plugin
name expression, or a bare plugin name to search). The migration source
of truth is the
cpv-the-skills-menu-create
skill bundled in this plugin; the full canonical spec lives at
the-skills-menu-spec.md.
Step 0 — Resolve the target
The argument can be any of:
| # | Form | Example |
|---|---|---|
| 1 | Explicit Git URL | https://github.com/<owner>/<repo>.git |
| 2 | Owner/repo slug | <owner>/<repo> |
| 3 | Local filesystem path | ~/code/my-plugin/, /abs/path/to/plugin |
| 4 | Plugin-in-marketplace expression | from the my-plugin in github.com/<owner>/<marketplace> |
| 5 | Bare plugin name | my-plugin (searches workspace + known marketplace caches) |
If no argument was supplied, ask the user plain-text:
Which plugin should I migrate to cpv-the-skills-menu method?
Give me a local path, a Git URL, or a plugin name.
Step 1 — Dispatch the skill
Invoke the backing skill, forwarding the user's entire argument
string verbatim — the target spec AND any trailing flags
(--full-cleanup, --force-dirty). The skill parses the flags
itself; dropping them silently changes the migration behaviour.
Skill({skill: "claude-plugins-validation:cpv-the-skills-menu-create", args: "<full-argument-string-including-any-flags>"})
Example — a path with both flags must arrive at the skill intact:
Skill({skill: "claude-plugins-validation:cpv-the-skills-menu-create", args: "~/code/my-plugin/ --full-cleanup --force-dirty"})
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 · 105 lines · 99 tokens per session scan A 3f1bfa67896c
cpv-the-skills-menu-create is a command published in the GitHub repository Emasoft/claude-plugins-validation (4 stars, last pushed yesterday), licensed MIT. It adds 99 tokens to every session and 1,307 once invoked, about $0.0005 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.