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-create-mono-agent)<a href="https://agentmods.dev/skills/emasoft/claude-plugins-validation/cpv-create-mono-agent"><img src="https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-create-mono-agent.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.00109 | $0.01730 |
| Opus 5 | $0.00055 | $0.00865 |
| Sonnet 5 | $0.00022 | $0.00346 |
| Haiku 4.5 | $0.00011 | $0.00173 |
Grade A, and why
cpv-create-mono-agent 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 6d 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cpv-create-mono-agent
Overview
Generates an ALL-IN-ONE AGENT: its skills: frontmatter lists every skill it needs
BY NAME, and its body is the routing layer that says WHEN to reach for each one. That
frontmatter list IS the preload — Claude Code injects each named skill's FULL content
into every invocation's cached prefix — so the agent is ready from turn 1 and never has
to fetch a skill mid-task.
A skill's content is NEVER copied into the agent. Not concatenated, not duplicated, not embedded. The reason is single-source-of-truth: a skill must stay INDEPENDENT so it can be shared by many agents and edited, fixed, or updated ONCE. An inlined copy is a second source that silently rots the moment the original changes, and with N agents inlining it there are N stale copies and no signal that any drifted. Referencing costs nothing, because the preload already puts the content in context.
SUPERSEDED — do not expect the old behaviour. Until TRDD-XUNZQ70I this generator CONCATENATED every skill body into one giant agent. That construction is now forbidden and there is exactly ONE version of the mechanism — no inlining path behind a flag.
The three architectures (canonical vocabulary)
| Architecture | skills: lists |
Skills execute in | Build it with |
|---|---|---|---|
| ALL-IN-ONE | every skill it needs | the same agent | this skill |
| ONE-FOR-ALL | every skill it needs | a separate subagent per skill | cpv-create-micro-agents-workflow |
| PLUGIN-OMNI | the plugin's the-skills-menu + the companion |
resolved at runtime from the menu | convert_agent.py --to plugin-omni |
ALL-IN-ONE and ONE-FOR-ALL differ in exactly ONE thing: WHERE a skill runs.
Prerequisites
uvon PATH- Target plugin path with
.claude-plugin/plugin.jsonand askills/directory - For the agent-scoped path: the source agent
.mdfile
Instructions
Pick the scope first — they use different scripts:
A. PLUGIN-WIDE (every non-meta skill the plugin ships):
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.
- 6d ago First seen · 135 lines · 109 tokens per session scan A 618f6fd524e3
cpv-create-mono-agent is a skill published in the GitHub repository Emasoft/claude-plugins-validation (4 stars, last pushed yesterday), licensed MIT. It adds 109 tokens to every session and 1,730 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 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…
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…
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…
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…