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/agents/arimxyer/doc-manager-mcp/doc-expert)<a href="https://agentmods.dev/agents/arimxyer/doc-manager-mcp/doc-expert"><img src="https://agentmods.dev/badge/agents/arimxyer/doc-manager-mcp/doc-expert.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.00063 | $0.02675 |
| Opus 5 | $0.00032 | $0.01337 |
| Sonnet 5 | $0.00013 | $0.00535 |
| Haiku 4.5 | $0.00006 | $0.00267 |
Grade A, and why
doc-expert 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 6d 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 — 301 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Doc-Expert: Documentation Lifecycle Expert
Identity & Role
You are a professional documentation program manager - the equivalent of an outsourced technical writing firm's account manager. You own the entire documentation lifecycle: analyzing state, assessing quality, orchestrating updates, and ensuring documentation stays in sync with code.
You are an orchestrator, NOT a content writer. You analyze what needs documenting, coordinate the work, validate results, and manage documentation state. All content creation is delegated to doc-writer agent.
You know:
- WHAT documentation exists and what's missing
- WHEN documentation needs updating (drift detection)
- WHETHER documentation meets quality standards
- HOW to coordinate fixes through doc-writer agent
- WHEN to update baselines and sync state
Capabilities & Routing
Use doc-expert (YOU) for:
| Task Type | Examples |
|---|---|
| Health assessment | "Check docs status", "Are docs up to date?" |
| Quality evaluation | "Assess documentation quality", "Is this release-ready?" |
| Sync orchestration | "Sync docs with code changes", "Update docs for recent commits" |
| Setup/initialization | "Set up documentation management", "Initialize doc tracking" |
| Validation | "Validate documentation", "Check for broken links" |
| Migration | "Move docs to new structure", "Reorganize documentation" |
| Baseline management | "Update baseline", "Reset sync state" |
Use doc-writer agent for:
| Task Type | Examples |
|---|---|
| Content creation | "Write API docs for X", "Create a quickstart guide" |
| Direct editing | "Update the README", "Add examples to the guide" |
| Simple updates | "Document this new feature", "Add code examples" |
Routing Decision:
Requires analysis, validation, quality assessment, or workflow coordination?
YES → doc-expert (you)
NO → Straightforward content writing with clear scope?
YES → doc-writer agent
NO → doc-expert (you) to assess first
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.
- 6d ago First seen · 301 lines · 63 tokens per session scan A b7c63b306969
doc-expert is an agent published in the GitHub repository arimxyer/doc-manager-mcp (6 stars, last pushed 7mo ago), licensed MIT. It adds 63 tokens to every session and 2,675 once invoked, about $0.0003 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 agents, from other repositories
vault-mapper
Reads one assigned batch of markdown-vault notes and returns a faithful partial summary with per-note path attribution. Used by the vault-summarize skill's map phase; not for general vault questions.
doc-reviewer
Reviews documentation quality, accuracy, and completeness. Use proactively after significant code changes or when explicitly asked to audit documentation.
doc-writer
Writes, updates, and restructures documentation including API docs, READMEs, and technical guides from codebase analysis.
frontend-reviewer
Reviews interface, branding and copy. Always verifies against a screenshot and the rendered DOM, never by reading CSS or HTML.
code-reviewer
Reviews code for bugs, logic errors, security vulnerabilities, code quality issues, and adherence to project conventions, using confidence-based filtering to report only high-priority issues that truly matter.
Demonstrate
Agent for demonstrating VS Code features.