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.
git clone --depth 1 https://github.com/arimxyer/doc-manager-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/commands/arimxyer/doc-manager-mcp/doc-quality)<a href="https://agentmods.dev/commands/arimxyer/doc-manager-mcp/doc-quality"><img src="https://agentmods.dev/badge/commands/arimxyer/doc-manager-mcp/doc-quality.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.00003 | $0.00507 |
| Opus 5 | $0.00002 | $0.00253 |
| Sonnet 5 | $0.00001 | $0.00101 |
| Haiku 4.5 | $0.00000 | $0.00051 |
Grade A, and why
doc-quality 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 7d 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.
What it actually says
Documentation Quality Assessment
Run comprehensive quality assessment against 7 criteria.
doc-expert agent Please run a documentation quality assessment.
Execute the quality assessment workflow:
-
Run Assessment: Execute
docmgr_assess_qualityto evaluate documentation against 7 criteria:- Relevance
- Accuracy
- Purposefulness
- Uniqueness
- Consistency
- Clarity
- Structure
-
Also Run Validation: Execute
docmgr_validate_docsto check:- Broken links
- Missing assets
- Code snippet syntax
- Convention compliance
-
Present Findings: Provide a comprehensive report with:
- Overall quality score
- Per-criterion scores
- Specific issues with file paths and line numbers
- Validation results
- Actionable recommendations
Format the output:
## Documentation Quality Report
### Overall Assessment: {excellent | good | fair | poor}
### Quality Scores
| Criterion | Score | Issues |
|-----------|-------|--------|
| Relevance | {score} | {count} |
| Accuracy | {score} | {count} |
| Purposefulness | {score} | {count} |
| Uniqueness | {score} | {count} |
| Consistency | {score} | {count} |
| Clarity | {score} | {count} |
| Structure | {score} | {count} |
### Validation Results
- **Links**: {count} checked, {count} issues
- **Assets**: {count} checked, {count} issues
- **Code Snippets**: {count} checked, {count} issues
### Specific Issues
**High Priority** (poor scores):
- {file}:{line} - {issue description}
**Medium Priority** (fair scores):
- {file}:{line} - {issue description}
### Recommendations
1. {actionable recommendation}
2. {actionable recommendation}
### Next Steps
- Fix high-priority issues first
- Run /doc-sync after fixes to update baseline
If user wants to fix issues:
Would you like me to help fix these issues? I can delegate the revisions to doc-writer agent.
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.
- 7d ago First seen · 81 lines · 3 tokens per session scan A 67ec145ad7db
doc-quality is a command published in the GitHub repository arimxyer/doc-manager-mcp (6 stars, last pushed 7mo ago), licensed MIT. It adds 3 tokens to every session and 507 once invoked, about $0.0000 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 commands, from other repositories
docs-add
Fetch a web source and make its Markdown searchable in this session. Accepts a built-in alias (e.g. "react"), an HTTPS URL, or "name url" to register a custom alias.
web-add
Fetch a web source and make its Markdown searchable in this session. Accepts a built-in alias (e.g. "react"), an HTTPS URL, or "name url" to register a custom alias.
docs-search
Search fetched Markdown by regex and pull surrounding context for the best hits. Optionally restrict to one source alias.
web-search
Search fetched web-source Markdown by regex and pull surrounding context for the best hits. Optionally restrict to one source alias.
docs-refresh
Re-fetch a cached source, ignoring the 7-day cache. Use when upstream content has changed.
web-refresh
Re-fetch a cached web source, ignoring the 7-day cache. Use when upstream content has changed.