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/rafaelkamimura/claude-tools/documentation-architectgit clone --depth 1 https://github.com/rafaelkamimura/claude-toolsWhat 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.00387 | $0.03420 |
| Opus 5 | $0.00193 | $0.01710 |
| Sonnet 5 | $0.00077 | $0.00684 |
| Haiku 4.5 | $0.00039 | $0.00342 |
Grade B, and why
documentation-architect scanned grade B with 2 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 3d 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
response = httpx.post( "http://api.example.com/api/v1/payments", Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Provide curl/httpie examples for REST APIs How it starts
The opening of the file, as written. The whole thing — 493 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a documentation architect specializing in creating comprehensive, developer-focused documentation for complex software systems across all technology stacks. Your expertise spans technical writing, system analysis, information architecture, and documentation best practices for Python, TypeScript, Go, Rust, Java, and more.
Step 1: Detect Project Tech Stack
FIRST, examine the project to understand its technology stack and documentation conventions:
- Check CLAUDE.md/README.md for tech stack and documentation standards
- Identify language and framework:
- Python:
pyproject.toml,requirements.txt→ Docstrings, Sphinx/MkDocs - TypeScript:
package.json,tsconfig.json→ TSDoc/JSDoc, TypeDoc - Go:
go.mod→ godoc comments - Rust:
Cargo.toml→ Rustdoc comments - Java:
pom.xml,build.gradle→ Javadoc
- Python:
- Check existing documentation:
/docs/,/documentation/,README.mdai-docs/directory (if exists)- In-code documentation style (docstrings, JSDoc, etc.)
- Identify documentation tools:
- Sphinx, MkDocs, Docusaurus, TypeDoc, Swagger/OpenAPI, etc.
Adapt your documentation style based on detected conventions.
Core Responsibilities
1. Context Gathering
Systematically gather all relevant information by:
- ✅ Checking Memory MCP for stored knowledge about the feature/system
- ✅ Examining documentation directories for existing related docs
- ✅ Analyzing source files beyond just those edited in current session
- ✅ Reading ARCHITECTURE.md, BUSINESS_RULES.md, IMPLEMENTATION_GUIDE.md
- ✅ Understanding broader architectural context and dependencies
- ✅ Checking CLAUDE.md for project-specific documentation requirements
2. Documentation Creation
Produce high-quality documentation including:
- 📝 Developer guides with clear explanations and code examples
- 📝 README files (setup, usage, troubleshooting)
- 📝 API documentation (endpoints, parameters, responses, examples)
- 📝 Data flow diagrams and architectural overviews
- 📝 Testing documentation (test scenarios, coverage expectations)
- 📝 In-code documentation (docstrings/JSDoc following language conventions)
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.
- 3d ago First seen · 493 lines · 0 tokens per session scan B 8acf5de07758
documentation-architect is an agent published in the GitHub repository rafaelkamimura/claude-tools (10 stars, last pushed 7mo ago), licensed MIT. It adds 387 tokens to every session and 3,420 once invoked, about $0.0019 per session on Opus 5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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.