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-refresh-readme)<a href="https://agentmods.dev/skills/emasoft/claude-plugins-validation/cpv-refresh-readme"><img src="https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-refresh-readme/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-refresh-readme"><img src="https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-refresh-readme.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.00055 | $0.00943 |
| Opus 5.5 | $0.00022 | $0.00377 |
| Sonnet 5.5 | $0.00011 | $0.00189 |
| Haiku 4.5 | $0.00006 | $0.00094 |
Grade A, and why
cpv-refresh-readme 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cpv-refresh-readme
Overview
Auto-refreshes the <!-- BEGIN AUTO-COMPONENTS --> block in a plugin's README.md so it never drifts out of sync with what the plugin actually ships (agents, skills, commands, hooks, MCP servers). Detects components from the filesystem and renders a markdown table inside the <!-- BEGIN/END AUTO-COMPONENTS --> markers. Custom prose around the block stays user-owned. Loaded dynamically via cpv-the-skills-menu, reached via the Manage → Refresh README menu branch.
Prerequisites
uvon PATH- Target plugin path with
README.md(or one will be created) - Optional:
<!-- BEGIN AUTO-COMPONENTS -->and<!-- END AUTO-COMPONENTS -->markers somewhere in the README (added on first run if missing)
Instructions
- Run
refresh_readme.pyagainst the target plugin path. - If markers exist, only the body between them is rewritten.
- If markers are missing, the block is appended at the end of the README on first run. You can move it wherever you want — subsequent runs preserve placement.
- For a CI gate, use
--checkto exit 1 if the README would change. - Wire into your publish.py as a pre-push gate so README never drifts in CI.
Copy this checklist and track your progress:
-
refresh_readme.pyinvoked - README updated (or
--checkconfirms no drift) - Optionally wired into publish.py Gate 8.5
Output
- An updated
README.mdwith the<!-- BEGIN AUTO-COMPONENTS -->block re-rendered. - Component table includes: agents, skills, commands, presence flags for hooks/MCP.
- Custom prose before/after the block is untouched.
Error Handling
| Error | Resolution |
|---|---|
| README.md missing | The script creates one on first run |
--check exit 1 |
README is out of date — run without --check to update |
| Markers in wrong place | Move them; subsequent runs preserve placement |
| Components missed | Confirm they're in canonical locations (agents/*.md, skills/<name>/SKILL.md, etc.) |
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 · 89 lines · 55 tokens per session scan A 685b2a555f6a
cpv-refresh-readme is a skill published in the GitHub repository Emasoft/claude-plugins-validation (4 stars, last pushed 3d ago), licensed MIT. It adds 55 tokens to every session and 943 once invoked, about $0.0002 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…