Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/esola-thomas/your-docs-mcpnpx agentmods add skills/esola-thomas/your-docs-mcp/doc-validateWrote 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/esola-thomas/your-docs-mcp/doc-validate)<a href="https://agentmods.dev/skills/esola-thomas/your-docs-mcp/doc-validate"><img src="https://agentmods.dev/badge/skills/esola-thomas/your-docs-mcp/doc-validate.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.1 | $0.00036 | $0.00683 |
| Opus 5 | $0.00018 | $0.00342 |
| Sonnet 5 | $0.00007 | $0.00137 |
| Haiku 4.5 | $0.00004 | $0.00068 |
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 5d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validate Documentation
Validate documentation files against the project's documentation standards.
Instructions
-
Determine scope:
- If a specific path is given, validate that file/directory
- If no path given, validate all docs in
docs/andexample/
-
Run the validation script if available:
python scripts/validate_docs.py $ARGUMENTS
- If script unavailable, perform manual checks:
Frontmatter Validation (Critical)
Check each markdown file for:
- YAML frontmatter exists (between
---markers) -
titlefield present and is a string -
categoryfield present and is a string -
tagsfield present and is an array -
orderfield present and is an integer
Markdown Formatting (Critical)
- Only one H1 (
#) per document - No skipped header levels (H1 -> H3 without H2)
- All code blocks have language specified
- Line length under 100 characters (except URLs, code, tables)
Content Structure (Warning)
- H1 matches the
titlefrontmatter field - Introduction present after H1
- Table of contents for docs with >3 sections
- Related resources section at end
Links (Critical)
- Internal links use relative paths with
.mdextension - Internal links resolve to existing files
- No "click here" link text
Output Format
Report findings in this format:
## Validation Results
### file-path.md
- [CRITICAL] Missing required frontmatter field: tags
- [WARNING] Line 45 exceeds 100 characters
- [INFO] Consider adding table of contents
### Summary
- Files checked: X
- Critical issues: X
- Warnings: X
- Passed: X
Severity Levels
| Level | Action Required | Examples |
|---|---|---|
| CRITICAL | Must fix before commit | Missing frontmatter, broken links, no H1 |
| WARNING | Should fix | Long lines, missing TOC |
| INFO | Optional | Unusual categories, style suggestions |
Auto-Fix Mode
If --fix is specified, automatically fix:
- Missing language tags on code blocks (add
text) - Trailing whitespace
- Missing blank lines around lists
- Inconsistent list markers (convert to
-)
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.
- 5d ago First seen · 103 lines · 0 tokens per session scan A b0d996d5f4d8
doc-validate is a skill published in the GitHub repository esola-thomas/your-docs-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 683 once invoked, about $0.0002 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.
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…