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-deterministic-codemod)<a href="https://agentmods.dev/skills/emasoft/claude-plugins-validation/cpv-deterministic-codemod"><img src="https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-deterministic-codemod/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-deterministic-codemod"><img src="https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-deterministic-codemod.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.00080 | $0.00977 |
| Opus 5.5 | $0.00032 | $0.00391 |
| Sonnet 5.5 | $0.00016 | $0.00195 |
| Haiku 4.5 | $0.00008 | $0.00098 |
Grade A, and why
cpv-deterministic-codemod 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cpv-deterministic-codemod
Overview
Bulk-applies the inverse of CPV's detection regexes — read-only audit becomes read-write fix at zero LLM cost. Designed for high-volume mechanical fixes where the cpv-plugin-fixer-agent agent is the wrong tool because the work is line-local and predictable. Addresses GitHub issue #17 and the high-volume Categories C and D of issue #16. Loaded dynamically via cpv-the-skills-menu, reached via the Fix → Deterministic codemod menu branch.
See subcommands for detail.
Subcommand table · Safety contract · Recommended workflow · When the codemod is the WRONG tool · Recovery
Prerequisites
uvon PATH- Target plugin path
- (Optional)
gitfor reviewing diffs before commit
Instructions
- Choose a subcommand:
backtick-to-link,add-toc,wrap-placeholder-paths,add-standard-sections,dedup-trailing-blanks,external-skip-list, orall. - Run dry-run first (default — no
--apply). Inspect the diff output. - Re-run with
--applyto write. A per-file backup is created under.cpv-codemod-backup/<timestamp>/<rel-path>. - Re-validate via
cpv-plugin-validation-skilland confirm finding counts dropped. - If something went wrong, restore from
.cpv-codemod-backup/<timestamp>/.
Copy this checklist and track your progress:
- Subcommand chosen
- Dry-run output reviewed
-
--applyrun (backup created) -
validate_pluginre-run, counts dropped - Backup deleted only after commit
Output
- Modified
.mdfiles at the chosen plugin path. - Per-file backups under
.cpv-codemod-backup/<timestamp>/<rel-path>(atomic, mirrors the plugin layout). - A unified-diff print of every change.
Error Handling
| Error | Resolution |
|---|---|
| Unknown subcommand | See the subcommands reference (linked above in Overview) |
| No diff produced | Codemod already idempotent on this tree |
| Permission denied on write | Check file permissions, or run from a writable workspace |
| Backup dir already exists | Re-runs create new timestamped dirs — old ones are kept until manual cleanup |
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 · 80 lines · 80 tokens per session scan A 0e5213c36f72
cpv-deterministic-codemod is a skill published in the GitHub repository Emasoft/claude-plugins-validation (4 stars, last pushed 3d ago), licensed MIT. It adds 80 tokens to every session and 977 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…