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-dashboard)<a href="https://agentmods.dev/commands/arimxyer/doc-manager-mcp/doc-dashboard"><img src="https://agentmods.dev/badge/commands/arimxyer/doc-manager-mcp/doc-dashboard.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.00007 | $0.00756 |
| Opus 5 | $0.00003 | $0.00378 |
| Sonnet 5 | $0.00001 | $0.00151 |
| Haiku 4.5 | $0.00001 | $0.00076 |
Grade A, and why
doc-dashboard 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 8d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Health Dashboard
Generate a comprehensive documentation health dashboard.
doc-expert agent Please generate a full documentation health dashboard.
Execute the following analysis and compile into a dashboard report:
1. Initialization Check
- Check if
.doc-manager/exists - If not initialized, report that and offer setup
2. Sync Status
Run docmgr_detect_changes and report:
- Total changed code files
- Affected documentation files
- Days since last baseline update
- Sync health indicator (🟢 Current | 🟡 Minor Drift | 🔴 Significant Drift)
3. Quality Metrics
Run docmgr_assess_quality and report:
- Score for each of the 7 criteria
- Overall quality assessment
- Trend indicators if available
4. Validation Status
Run docmgr_validate_docs and report:
- Links checked and issues found
- Assets checked and issues found
- Code snippets checked and issues found
5. Compile Dashboard
Format as:
# 📊 Documentation Health Dashboard
**Project**: [name]
**Platform**: [platform]
**Last Sync**: [date/time]
## Health Summary
| Indicator | Status | Details |
|-----------|--------|---------|
| Sync Status | [🟢/🟡/🔴] | [X files changed] |
| Quality | [🟢/🟡/🔴] | [Overall: good/fair/poor] |
| Validation | [🟢/🟡/🔴] | [X issues found] |
## Sync Status
- **Changed Code Files**: X
- **Affected Doc Files**: X
- **Days Since Sync**: X
## Quality Scores
| Criterion | Score | Issues |
|-----------|-------|--------|
| Relevance | [🟢/🟡/🔴] | X |
| Accuracy | [🟢/🟡/🔴] | X |
| Purposefulness | [🟢/🟡/🔴] | X |
| Uniqueness | [🟢/🟡/🔴] | X |
| Consistency | [🟢/🟡/🔴] | X |
| Clarity | [🟢/🟡/🔴] | X |
| Structure | [🟢/🟡/🔴] | X |
**Overall Quality**: [excellent/good/fair/poor]
## Validation Results
| Check | Scanned | Issues |
|-------|---------|--------|
| Links | X | X |
| Assets | X | X |
| Code Snippets | X | X |
## Top Issues (if any)
1. [Most critical issue with file:line]
2. [Second issue]
3. [Third issue]
## Recommended Actions
1. [Highest priority action]
2. [Second priority action]
3. [Third priority action]
## Quick Commands
| Command | Action |
|---------|--------|
| `/doc-sync` | Sync documentation with code |
| `/doc-quality` | Detailed quality report |
| `/doc-status` | Quick status check |
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.
- 8d ago First seen · 111 lines · 7 tokens per session scan A 5a22b30dd5da
doc-dashboard is a command published in the GitHub repository arimxyer/doc-manager-mcp (6 stars, last pushed 7mo ago), licensed MIT. It adds 7 tokens to every session and 756 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.