agentmods.dev

doc-validate

A documentation checker for finding formatting problems, broken links, missing navigation files, empty sections, and related issues in project documents.

In plain words
What is it for?
Linting documents, checking links and document relationships, finding orphaned pages or cycles, checking required sections, and running a broader documentation review.
Why use it?
It makes documentation problems visible before they confuse readers or leave the documentation structure incomplete.

Skill for Claude CodeCodex

16 4mo ago A scan 216 tokens original MIT
View the source file dapi/claude-code-marketplace
Install

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.

agentmods
npx agentmods add skills/dapi/claude-code-marketplace/doc-validate
Any agent
npx skills add dapi/claude-code-marketplace --skill doc-validate
Clone the repo
git clone --depth 1 https://github.com/dapi/claude-code-marketplace

Made for: Claude Code, Codex.

Per session 216 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,422 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00216 $0.03422
Opus 5 $0.00108 $0.01711
Sonnet 5 $0.00043 $0.00684
Haiku 4.5 $0.00022 $0.00342

Measured 2d ago against content hash 9c6f831affe3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

doc-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 2d ago.

The scan reads SKILL.md. This mod also ships 3 executable files (doc_validate.rb, spec/doc_validator_spec.rb, spec/spec_helper.rb), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

doc-validate/skills/doc-validate/SKILL.md · 417 lines

How it starts

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

Documentation Validation Skill

Комплекс команд /doc:* для автоматической и интерактивной проверки качества проектной документации.

Быстрый старт

# Быстрая проверка перед коммитом
/doc:lint

# Проверка графа связей
/doc:links

# Полный аудит (все проверки)
/doc:review

Команды

/doc:lint — Проверка форматирования

Модель: haiku (быстро, дёшево) Время: < 30 сек для 100 файлов

Проверки:

  • Битые внутренние ссылки [text](file.md)
  • Несуществующие файлы в навигации
  • Нарушения naming conventions (NN_TITLE.md для корневых)
  • Пустые секции (## без контента)
  • TODO/FIXME без ссылки на issue
  • Отсутствие обязательных секций

Пример вывода:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 [LINT-001] Битая ссылка
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

 03_REQUIREMENTS.md:45
   > [см. архитектуру](architecture/MISSING.md)

❌ Файл не существует: architecture/MISSING.md

[f]ix  [s]kip  [i]gnore  [e]dit  [g]ithub issue  [x]plain
> _

/doc:links — Граф связей

Модель: haiku Время: < 30 сек для 100 файлов

Проверки:

  • Orphan-документы (без входящих ссылок)
  • Dead-ends (без исходящих ссылок)
  • Циклические зависимости
  • Полнота навигации в README

Исключения (не считаются orphans/dead-ends):

  • README.md, CHANGELOG.md
  • **/GLOSSARY.md, **/INDEX.md
  • Конфигурируется в .docvalidate.yml

Пример вывода:

 Граф документации
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Всего документов: 35
Связей: 128

⚠️ Orphans (нет входящих ссылок):
  - research/old_analysis.md
  - data/transaction-analysis.md

⚠️ Dead-ends (нет исходящих ссылок):
  - architecture/wallet/COMPONENTS.md

✅ README навигация: 28/35 документов (80%)

/doc:terms — Терминология ✅

Модель: sonnet (или haiku для базовых проверок) Требует: глоссарий в 02_GLOSSARY.md

Проверки:

  • Термины из глоссария используются единообразно
  • Обнаружение запрещённых синонимов (кошелёк/wallet/бумажник)
  • Новые термины не в глоссарии (выделенные bold)
  • Покрытие глоссария (% используемых терминов)

Read the full file on GitHub · 417 lines

Files

What ships with it

11 files 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.

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. 2d ago First seen · 417 lines · 216 tokens per session scan A 9c6f831affe3

Subscribe to this mod's changes

doc-validate is a skill published in the GitHub repository dapi/claude-code-marketplace (16 stars, last pushed 4mo ago), licensed MIT. It adds 216 tokens to every session and 3,422 once invoked, about $0.0011 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-30.

Writing and docs
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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.

obra/superpowers · 37 tokens

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.

microsoft/vscode · 62 tokens

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.

microsoft/vscode · 51 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens