cpv-fix-validation

cpv-fix-validation is a skill for Claude Code from Emasoft/claude-plugins-validation. It costs 69 tokens per session (1,984 once invoked), scanned A, original, MIT.

A lookup guide that connects validation errors to specific repair instructions. It also defines which files may be linted, formatted, or edited by hand during repairs.

In plain words
What is it for?
Use it after a plugin validation report to find repair steps for critical, major, minor, or small style findings.
Why use it?
Validation reports can contain different kinds of findings, and broad formatting can damage structured Markdown, configuration, or frontmatter. The guide helps apply a focused fix without rewriting unrelated content.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter. Also seen: mentions CLAUDE.md.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the claude-plugins-validation plugin — 52 skills, 14 commands, 14 agents shipped together

Good fit Use it after a plugin validation report to find repair steps for critical, major, minor, or small style findings.

Compare 6 skills from other repositories ↓
Install

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.

Claude Code
/plugin marketplace add Emasoft/claude-plugins-validation
Claude Code
/plugin install claude-plugins-validation

Made for: Claude Code.

Or install claude-plugins-validation, the plugin that ships this one along with the rest of its 52 skills, 14 commands, 14 agents.

Wrote 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.

agentmods badge for cpv-fix-validation

README.md
[![agentmods](https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-fix-validation/github.svg)](https://agentmods.dev/skills/emasoft/claude-plugins-validation/cpv-fix-validation)
Your own site
<a href="https://agentmods.dev/skills/emasoft/claude-plugins-validation/cpv-fix-validation"><img src="https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-fix-validation/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.

agentmods 80×15 button for cpv-fix-validation

Your own site · 80×15
<a href="https://agentmods.dev/skills/emasoft/claude-plugins-validation/cpv-fix-validation"><img src="https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-fix-validation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 69 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,984 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00069 $0.01984
Opus 5.5 $0.00028 $0.00794
Sonnet 5.5 $0.00014 $0.00397
Haiku 4.5 $0.00007 $0.00198

Measured 26d ago against content hash 3ef4c4f1f0d6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

cpv-fix-validation 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 26d 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.

skills/cpv-fix-validation/SKILL.md · 81 lines

How it starts

The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Fix Validation — Error-to-Fix Index

Overview

Central error-to-fix lookup. Maps validation errors to fix guides in references/.

Formatter canon — lint only, NEVER format (user directive)

NEVER run a FORMATTER on any file: no ruff format, no prettier, no mdformat, no markdown formatter. Formatters reflow content and corrupt the structured Markdown that skills, agents, TRDDs, wikimem, obsidian notes, and YAML frontmatter depend on.

  • Markdown / mdz / docs / TRDD / wikimem: lint-only. Run markdownlint in REPORT mode, then fix each finding BY HAND with Edit. NEVER markdownlint --fix.
  • Python / JS/TS: the LINTER's autofix is allowed — ruff check --fix, eslint --fix. NEVER the FORMATTER (ruff format / prettier).
  • JSON / YAML / config: lint/report only, fix by hand. No prettier --write.

Why: a formatter (and markdown --fix) rewrites files opaquely and breaks the careful structure the author maintains. This is the same discipline as the fixer-agent scope guard ("never reformat a file you weren't sent to fix").

Prerequisites

  • Report from /cpv-validate-*
  • Access to references/

Instructions

The token-economical fix flow (validate → ledger → MECH → INTEL read-once → delta → terminate):

  1. Validate → compact ledger, not the full report. remote_validation.py <mode> <root> --strict --json > <findings.json>, then cpv_fix_ledger.py build --json <findings.json> --text <ledger.txt>; read <ledger.txt> (by-file, MECH/INTEL split, BLOCKING pre-tagged) — never ingest the full .md report each iteration (cost ≈ turns × per-turn-context).
  2. MECH first (zero-LLM). Auto-apply the mech bucket with cpv_codemod.py apply --json <findings.json> --apply before spending any model tokens.
  3. INTEL fix-as-you-go, read-once. Per intel file: read ONLY the finding line ranges (tldr slice / Read offset+limit), apply ALL its fixes in the SAME turn, never re-read. The recipe is the ledger's inline suggestion; open plugin-error-index.md / marketplace-error-index.md ONCE per rule-TYPE (jump via TOC), not per finding. For category: architecture, use cpv-migrate-marketplace-architecture.
  4. Delta re-validate → terminate. Re-validate, rebuild the delta ledger, feed cpv_fix_loop_state.py record (CONVERGED / CYCLE / STALLED). Full loop: iterative-fix-loop.

Read the full file on GitHub · 81 lines

Changes

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.

  1. 26d ago Changed 3ef4c4f1f0d6
  2. 1mo ago First seen · 81 lines · 69 tokens per session scan A 07f894c7642e

Subscribe to this mod's changes

cpv-fix-validation is a skill published in the GitHub repository Emasoft/claude-plugins-validation (4 stars, last pushed 3d ago), licensed MIT. It adds 69 tokens to every session and 1,984 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.

Related

Other skills, from other repositories

adversarial-reviewer

Stress-test a code change for concrete correctness defects, unsafe assumptions, and failure modes. Use when the user explicitly asks for an adversarial review, a deep bug hunt, or to tear a change apart, or to check your own change before submitting it. Do not use for ordinary review, style feedback, or general…

emdash-cms/emdash · 72 tokens

gsd-ns-review

Invoke this Pi skill with /skill:gsd-ns-review.

open-gsd/gsd-core · 16 tokens

gitnexus

A code-graph analysis add-on for examining an existing codebase, including symbols, call paths, execution flows, and effects across repositories. It can query GitNexus through its command-line or MCP interfaces.

hashgraph-online/awesome-codex-plugins · 58 tokens

issue

Use when starting a chain from a GitHub issue — turning an issue URL or number into a triaged, planned, dispatched, and reviewed pull request. Classifies the thread (bug → root-cause discipline, feature → plan chain, question → drafted reply), synthesizes a spec from the issue's own acceptance criteria, then runs the…

jeremylongshore/tons-of-skills-marketplace · 115 tokens

cleanup-code-inspections

Reduce technical debt and improve code quality by systematically resolving static analysis warnings.

flutter/flutter-intellij · 19 tokens

superlint

This skill describes the mandatory standard operating procedure for using our internal SuperLint tool. Use this when tasks require fixing code quality issues according to corporate standards.

mgechev/skillgrade · 0 tokens