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-validate-plugin-folder)<a href="https://agentmods.dev/skills/emasoft/claude-plugins-validation/cpv-validate-plugin-folder"><img src="https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-validate-plugin-folder/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-validate-plugin-folder"><img src="https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-validate-plugin-folder.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.00132 | $0.01765 |
| Opus 5.5 | $0.00053 | $0.00706 |
| Sonnet 5.5 | $0.00026 | $0.00353 |
| Haiku 4.5 | $0.00013 | $0.00177 |
Grade A, and why
cpv-validate-plugin-folder 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cpv-validate-plugin-folder
Read-only. Runs one script and reports what it printed.
Overview
One command, full coverage, for one folder shape at a time. The skill
composes CPV's existing validators — plugin --strict, marketplace,
skill --strict, and the full security scan — behind a single entry
point (cpv_validate_plugin_folder.py) so a caller never has to know in
advance which validator applies. It never implements a rule of its own:
every finding traces back to an existing CPV validator, and the skill's
only job is detecting the folder's shape, dispatching the right
validator combination, merging the results, and reporting a single
severity table with the report path and the fixer to run next.
Prerequisites
- A Python 3 interpreter on
PATH(the script is invoked aspython3 "${CLAUDE_PLUGIN_ROOT}/scripts/cpv_validate_plugin_folder.py"). gitonPATHwhen the target is a remote URL or anowner/reposlug — the script clones it into a temp sandbox before scanning.- No other setup: the script requires no network access for a local path, no installation step, and never runs the plugin/skill/repo it scans.
Instructions
-
Run exactly this, substituting the user's argument when they gave one and omitting it entirely when they did not — the script resolves the default itself, so do not guess a path on its behalf:
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/cpv_validate_plugin_folder.py" [folder-path-or-repo-url] -
Relay the script's output verbatim in substance: the severity table, the report path, and the suggested fixer for each failing scan.
-
Stop there. Do not summarise findings away, do not re-run individual validators, and do not fix anything — this skill is the read-only half. Fixing is a separate, explicit user decision, which is why the script names the fixer instead of dispatching it.
The skill is done when the table, the report path and any fixer suggestions have been relayed; a non-zero exit is a verdict to report, not an error to retry.
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 · 153 lines · 132 tokens per session scan A e32afe798134
cpv-validate-plugin-folder is a skill published in the GitHub repository Emasoft/claude-plugins-validation (4 stars, last pushed 3d ago), licensed MIT. It adds 132 tokens to every session and 1,765 once invoked, about $0.0005 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
hermes-diagnostic-review
Use when running a read-only diagnostic review of recent Hermes sessions to find recurring mistakes, failed tool calls, and repeated fixes, then propose suggestion-only improvements and reusable skills. Human-gated; never auto-applies.
oci-drawio-icon-native
Build and validate OCI draw.io diagrams in icon-native mode so they never depend on mxgraph.oci. runtime libraries. Use when authoring or fixing Oracle Cloud architecture diagrams in draw.io that must render portably.
instruction-eval
Change one condition an agent runs under (instruction text, the reference material instructions point at, MCP tools and permissions, hooks, skill files), then run the same prompts before and after, several times each, to see what actually changes. Produces an HTML report showing both arms' answers side by side. Use…
worth-building
Decide how elaborate to build something (simple vs. robust) and return a concrete, PoC-shaped proposal at that level — not over- or under-engineered, but right-sized. Use whenever someone is building something and the investment level is unclear: "quick or proper?", "MVP vs. real product", "is this over-engineering?"…
django-ticket-triage
Analyze a Django Trac ticket and produce a triage recommendation report — duplicate search, related PRs, forum threads, and the affected source code. Use when the user gives a Django ticket number, or asks whether a ticket is valid, a duplicate, or ready for a triage stage.
gh-issues
Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5]…