A document-checking skill that verifies a finished document against its source and against rules for style, tone, length, format, and focus. It first checks whether important claims are supported, then reviews compliance and can produce a corrected copy.

Use it to validate documents, create grounding and consistency reports, make a compliance checklist, summarise the result, and produce a best-effort corrected version.

It helps catch unsupported statements, contradictions, and formatting or style problems before a document is delivered. The source check is separate from the writing-quality checks, so both kinds of errors are reviewed.

validate — Skill for Claude Code by stellarshenson/claude-code-plugins

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 stellarshenson/claude-code-plugins

Claude Code

/plugin install document-processing

Made for: Claude Code.

Or install document-processing, the plugin that ships this one along with the rest of its 5 skills, 5 commands.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/stellarshenson/claude-code-plugins/validate/github.svg)](https://agentmods.dev/skills/stellarshenson/claude-code-plugins/validate)

Your own site

<a href="https://agentmods.dev/skills/stellarshenson/claude-code-plugins/validate"><img src="https://agentmods.dev/badge/skills/stellarshenson/claude-code-plugins/validate/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/stellarshenson/claude-code-plugins/validate"><img src="https://agentmods.dev/badge/skills/stellarshenson/claude-code-plugins/validate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 85 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,435 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.

Model	Per session	Once invoked
Fable 5.1	$0.00085	$0.02435
Opus 5.5	$0.00034	$0.00974
Sonnet 5.5	$0.00017	$0.00487
Haiku 4.5	$0.00009	$0.00244

Measured 1mo ago against content hash 903aa2987575, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

plugins/document-processing/skills/validate/SKILL.md · 210 lines

How it starts

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

Validate Skill

Two layers:

Grounding — full grounding chain from grounding skill: extract-claims → ground → check-consistency. Every load-bearing claim verified against source(s), plus document checked against itself. Outputs claims.json, grounding-report.md, consistency-report.md. Not re-implemented here — delegated to grounding skill verbatim, including its three core verdict rules, OCR fallback chain, semantic-consent gate.
Compliance — tone, style, length, format, focus, custom rules (project criteria). Part grounding does not do; makes this validate skill rather than grounding skill.

Skill gathers criteria (Phase 0), runs full grounding chain through grounding skill (Phase 2), adds compliance layer (Phase 3), produces verdict (Phase 4), ships best-effort corrected copy (Phase 5).

Output style (MANDATORY for all generated artefacts)

Every file this skill writes (grounding-report.md, consistency-report.md, compliance-checklist.md, validation-summary.md, criteria.md) uses telegram-style: short clauses, drop articles/copulas where meaning stays clear, one fact per line, bullets not paragraphs, concrete numbers over adjectives, no hedging ("may"/"might"), imperative actions. Reviewers skim for verdicts - prose costs attention.

Pre-flight install (MANDATORY - run every session, no asking)

python3 -m pip install --user --upgrade stellars-claude-code-plugins 2>&1 | tail -1
LIB=$(python3 -c "import importlib.metadata as m;print(m.version('stellars-claude-code-plugins'))" 2>/dev/null) || { echo "FATAL: toolkit unavailable"; exit 1; }
PLUG=$(grep -m1 '"version"' "${CLAUDE_PLUGIN_ROOT}/.claude-plugin/plugin.json" 2>/dev/null | cut -d'"' -f4)
OLDER=$(printf '%s\n%s\n' "$LIB" "$PLUG" | sort -V | head -1)
[ -n "$PLUG" ] && [ "$LIB" != "$PLUG" ] && [ "$OLDER" = "$LIB" ] && { echo "STALE: library $LIB older than plugin $PLUG - refusing to run on an outdated CLI; re-run the upgrade"; exit 1; }
echo "toolkit $LIB"

Read the full file on GitHub · 210 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.

1mo ago First seen · 210 lines · 85 tokens per session scan A 903aa2987575

Subscribe to this mod's changes

validate is a skill published in the GitHub repository stellarshenson/claude-code-plugins (4 stars, last pushed today), licensed MIT. It adds 85 tokens to every session and 2,435 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-09-05.

Documents Writing and docs

orbit-notion

Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…

nexu-io/open-design · 117 tokens

instrument-data-to-allotrope

Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…

anthropics/knowledge-work-plugins · 123 tokens

legal-hold

Issue, refresh, release, or report on legal holds — drafts the hold notice as .docx, updates legalhold fields in log.yaml, and calendars the next refresh. Use when the user says "issue a hold", "refresh hold", "release hold", or asks for a portfolio-wide hold status report.

anthropics/claude-for-legal · 68 tokens

validate