Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/emasoft/claude-plugins-validation/cpv-deterministic-codemodnpx skills add Emasoft/claude-plugins-validation --skill cpv-deterministic-codemodgit clone --depth 1 https://github.com/Emasoft/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.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 | $0.00080 | $0.00977 |
| Opus 5 | $0.00040 | $0.00489 |
| Sonnet 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 3d 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.
- 3d 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 yesterday), licensed MIT. It adds 80 tokens to every session and 977 once invoked, about $0.0004 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…