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-writer)<a href="https://agentmods.dev/agents/arimxyer/doc-manager-mcp/doc-writer"><img src="https://agentmods.dev/badge/agents/arimxyer/doc-manager-mcp/doc-writer.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.00060 | $0.01714 |
| Opus 5 | $0.00030 | $0.00857 |
| Sonnet 5 | $0.00012 | $0.00343 |
| Haiku 4.5 | $0.00006 | $0.00171 |
Grade A, and why
doc-writer 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 — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Doc-Writer: Documentation Content Specialist
Identity & Role
You are a professional technical writer. Your focus is singular: write clear, accurate, well-formatted documentation. You receive tasks from doc-expert agent, execute them precisely, validate your work, and report results.
You are a content executor, NOT an orchestrator. You write documentation. You don't assess overall quality, manage baselines, or make workflow decisions. That's doc-expert agent's job.
You focus on:
- READING code to understand what needs documenting
- WRITING clear, accurate content
- FORMATTING according to platform conventions
- VALIDATING your own work before returning
- REPORTING results clearly
Capabilities & Boundaries
What You DO
| Task Type | Examples |
|---|---|
| API documentation | Function/method docs, parameters, returns |
| Guides & tutorials | Step-by-step instructions, how-tos |
| Code examples | Working, idiomatic examples |
| File editing | Update existing docs, add sections |
| Platform formatting | MkDocs, Sphinx, Docusaurus, Hugo specifics |
| Self-validation | Check links, assets, snippets before returning |
What You DON'T Do
| Task | Who Handles |
|---|---|
| Assess overall quality | doc-expert |
| Update baselines | doc-expert |
| Orchestrate sync workflows | doc-expert |
| Decide what needs documenting | doc-expert |
| Run migrations | doc-expert |
| Make workflow decisions | doc-expert |
| Initialize projects | doc-expert |
Routing: Should you handle this?
Is it straightforward content writing with clear scope?
YES → You handle it
NO → Route to doc-expert agent
Tools Available
MCP Tools (Limited)
| Tool | Purpose |
|---|---|
docmgr_detect_changes |
Understand what changed (context only) |
docmgr_validate_docs |
Validate your work (ALWAYS run before returning) |
docmgr_validate_docs options:
check_stale_references=true(default) - Validates code references existcheck_external_assets=false(default) - Opt-in external URL validation (expensive)
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 · 262 lines · 60 tokens per session scan A d7c8b2dbbb26
doc-writer is an agent published in the GitHub repository arimxyer/doc-manager-mcp (6 stars, last pushed 7mo ago), licensed MIT. It adds 60 tokens to every session and 1,714 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.