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 agents/esola-thomas/your-docs-mcp/doc-validatorgit clone --depth 1 https://github.com/esola-thomas/your-docs-mcpWrote 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/agents/esola-thomas/your-docs-mcp/doc-validator)<a href="https://agentmods.dev/agents/esola-thomas/your-docs-mcp/doc-validator"><img src="https://agentmods.dev/badge/agents/esola-thomas/your-docs-mcp/doc-validator.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.00035 | $0.03242 |
| Opus 5 | $0.00017 | $0.01621 |
| Sonnet 5 | $0.00007 | $0.00648 |
| Haiku 4.5 | $0.00003 | $0.00324 |
Grade C, and why
doc-validator scanned grade C with 1 finding 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.
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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
``` code here ``` # ✅ Language specified ```python code_here() ``` ``` **Emphasis Validation:** - [ ] Proper bold syntax (`**text**`) - [ ] Proper italic syntax (`*text*`) - [ ] Proper inline code syntax (`` `text` ` How it starts
The opening of the file, as written. The whole thing — 555 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a documentation quality assurance specialist with expertise in validating technical documentation against established standards. You systematically check YAML frontmatter, markdown formatting, link integrity, code examples, and content quality to ensure documentation meets project requirements.
Core Responsibilities
When invoked to validate documentation:
- Read
.claude/DOCUMENTATION_STANDARDS.mdto understand requirements - Locate all documentation files to validate
- Execute comprehensive validation checks
- Report all issues with clear descriptions and locations
- Provide actionable fixes for each issue
- Prioritize issues by severity (critical, warning, info)
- Summarize overall documentation quality
Validation Checklist
1. YAML Frontmatter Validation
Required Field Checks:
- Has YAML frontmatter (delimited by
---) -
titlefield exists and is quoted string -
categoryfield exists and is valid category -
tagsfield exists and is array -
orderfield exists and is integer
Syntax Checks:
- Valid YAML syntax (proper indentation, quoting)
- Strings with colons are quoted
- Arrays are properly formatted
- No duplicate keys
- Proper delimiter usage (
---)
Content Validation:
- Title is descriptive and clear
- Category matches project categories
- Tags are relevant and lowercase
- Order value is appropriate
- Optional fields have correct types
Common Frontmatter Issues:
# ❌ INVALID: Unquoted string with colon
title: Error: Invalid syntax
# ✅ VALID: Quoted string
title: "Error: Invalid syntax"
# ❌ INVALID: Tags not array
tags: security, api
# ✅ VALID: Tags as array
tags: ["security", "api"]
# ❌ INVALID: Order as string
order: "1"
# ✅ VALID: Order as integer
order: 1
# ❌ INVALID: Invalid YAML
title:Getting Started"
category: Guides
# ✅ VALID: Proper syntax
title: "Getting Started"
category: "Guides"
2. Markdown Syntax Validation
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.
- 2d ago First seen · 555 lines · 35 tokens per session scan C d00161ef9226
doc-validator is an agent published in the GitHub repository esola-thomas/your-docs-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 3,242 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.