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-add-dependency)<a href="https://agentmods.dev/skills/emasoft/claude-plugins-validation/cpv-add-dependency"><img src="https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-add-dependency/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-add-dependency"><img src="https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-add-dependency.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.00064 | $0.01057 |
| Opus 5.5 | $0.00026 | $0.00423 |
| Sonnet 5.5 | $0.00013 | $0.00211 |
| Haiku 4.5 | $0.00006 | $0.00106 |
Grade A, and why
cpv-add-dependency 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cpv-add-dependency
Overview
Adds one or more plugin dependencies to a target plugin's plugin.json::dependencies array. Two input modes that can be combined; the engine deduplicates by name (last-write-wins), sorts the result alphabetically, writes atomically, and rolls back from a .bak if the post-write validation introduces any new CRITICAL/MAJOR finding. Loaded dynamically via cpv-the-skills-menu, reached via the Create → Add dependencies menu branch.
Prerequisites
uvon PATH- Target plugin path with
.claude-plugin/plugin.json - For
--fromgit URLs: network access andgiton PATH - For cross-marketplace deps: the hosting marketplace's
marketplace.json::allowCrossMarketplaceDependenciesOnallowlist updated
Instructions
- Always start with
--dry-runto preview the diff againstplugin.json. - Choose
--add(explicit specs) and/or--from(copy from another plugin). - Use kebab-case names; versions accept any semver-range expression (
~1.2.0,^2.0,>=1.4). - Run the real invocation; the script writes atomically (tmp + rename) and re-runs
validate_plugin --strict. - If exit code is 3 (rollback), inspect the diff, narrow the spec, and re-try.
- For unversioned bare-string adds,
validate_plugin --strictemits a WARNING that the dependency auto-tracks the latest upstream tag. The only valid resolution is to pin a semver range (name@@~1.2.0); there is no config opt-out (cpv.allow_unversioned_dependencieswas removed in TRDD-02e1672b and is now ignored with a[RC-DEPRECATED-OPTOUT]deprecation WARNING if present).
Copy this checklist and track your progress:
- Dry-run reviewed
- Explicit specs or
--fromsource confirmed - Real invocation run
- Exit code 0 (or 3 → analyze rollback reason)
-
validate_plugin --strictre-run on target
Output
- Updated
plugin.json::dependenciesarray, sorted alphabetically, deduplicated by name. - Atomic write via tmp + rename.
.bakleft next toplugin.jsonafter a successful update so a human can roll back manually if needed.- Exit code 0 on success, 1 on bad args, 2 on
--fromsource unreadable, 3 on rollback after regression, 4 on atomic-write failure.
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 · 78 lines · 64 tokens per session scan A 02ce9114a6cf
cpv-add-dependency is a skill published in the GitHub repository Emasoft/claude-plugins-validation (4 stars, last pushed 3d ago), licensed MIT. It adds 64 tokens to every session and 1,057 once invoked, about $0.0003 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-08-31.
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…