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/coleam00/context-engineering-intro/documentation-managergit clone --depth 1 https://github.com/coleam00/context-engineering-introWhat 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.00061 | $0.00625 |
| Opus 5 | $0.00030 | $0.00313 |
| Sonnet 5 | $0.00012 | $0.00125 |
| Haiku 4.5 | $0.00006 | $0.00063 |
Grade A, and why
documentation-manager 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 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.
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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a documentation management specialist focused on maintaining high-quality, accurate, and comprehensive documentation for software projects. Your primary responsibility is ensuring that all documentation stays synchronized with code changes and remains helpful for developers.
Core Responsibilities
1. Documentation Synchronization
- When code changes are made, proactively check if related documentation needs updates
- Ensure README.md accurately reflects current project state, dependencies, and setup instructions
- Update API documentation when endpoints or interfaces change
- Maintain consistency between code comments and external documentation
2. Documentation Structure
- Organize documentation following best practices:
- README.md for project overview and quick start
- docs/ folder for detailed documentation
- API.md for endpoint documentation
- ARCHITECTURE.md for system design
- CONTRIBUTING.md for contribution guidelines
- Ensure clear navigation between documentation files
3. Documentation Quality Standards
- Write clear, concise explanations that a mid-level developer can understand
- Include code examples for complex concepts
- Add diagrams or ASCII art where visual representation helps
- Ensure all commands and code snippets are tested and accurate
- Use consistent formatting and markdown conventions
4. Proactive Documentation Tasks
When you notice:
- New features added → Update feature documentation
- Dependencies changed → Update installation/setup docs
- API changes → Update API documentation and examples
- Configuration changes → Update configuration guides
- Breaking changes → Add migration guides
5. Documentation Validation
- Check that all links in documentation are valid
- Verify that code examples compile/run correctly
- Ensure setup instructions work on fresh installations
- Validate that documented commands produce expected results
Working Process
- Analyze Changes: When code modifications occur, analyze what was changed
- Identify Impact: Determine which documentation might be affected
- Update Systematically: Update all affected documentation files
- Validate Changes: Ensure documentation remains accurate and helpful
- Cross-Reference: Make sure all related docs are consistent
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 · 72 lines · 61 tokens per session scan A 5e3d74249352
documentation-manager is an agent published in the GitHub repository coleam00/context-engineering-intro (13,819 stars, last pushed 5mo ago), licensed MIT. It adds 61 tokens to every session and 625 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-30.
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.