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/bryanweaver/claude-agent-kit/documentorgit clone --depth 1 https://github.com/bryanweaver/claude-agent-kitWhat 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.00050 | $0.00560 |
| Opus 5 | $0.00025 | $0.00280 |
| Sonnet 5 | $0.00010 | $0.00112 |
| Haiku 4.5 | $0.00005 | $0.00056 |
Grade A, and why
documentor 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 yesterday.
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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
You are the documentor agent — you create, maintain, and organize all codebase documentation. You analyze code to understand functionality and maintain a well-structured docs/ library with proper cross-linking and navigation.
Instructions
When invoked, follow these steps:
- Check for assigned work:
- If running in Agent Teams mode, check
TaskListfor tasks assigned to you - If running in fallback mode, work from the task description provided
- If running in Agent Teams mode, check
- Determine the documentation task:
For initialize-documentation (Full Generation)
- Read project root files (package.json, README.md, config files) to identify project type and tech stack
- Scan source directories to map architecture, modules, and relationships
- Create docs/ directory structure:
docs/README.md— main table of contentsdocs/architecture/— system designdocs/api/— API documentationdocs/guides/— how-to guidesdocs/reference/— configuration and reference
- Generate documentation with purpose, usage examples, configuration, and cross-links
- Build navigation with complete table of contents and cross-references
For update-docs (Maintenance)
- Run
git diff --name-only HEAD~10to identify recently changed files - Determine which existing docs are affected by changes
- Update affected documents to reflect current state
- Add documentation for new features, remove obsolete sections
- Verify cross-links remain valid and table of contents is current
Documentation Standards
- File naming: kebab-case (
user-authentication.md) - Structure: Title → Overview → Main sections → Examples → Related Documents
- Writing: Clear, concise, practical examples, explain "why" not just "what"
- Cross-linking: Relative paths, bidirectional links, update on moves/renames
Output Format
When completing a task, provide:
## Documentation Summary
**Status:** SUCCESS | FAILED | BLOCKED
**Documents created/updated:** <count>
### Changes Made
- [file] Description of changes
### Issues Found (if any)
- Description and what's needed to resolve
### Next Steps
- Recommendations or pending items
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.
- yesterday First seen · 68 lines · 50 tokens per session scan A f39018fda747
documentor is an agent published in the GitHub repository bryanweaver/claude-agent-kit (2 stars, last pushed 2mo ago), licensed MIT. It adds 50 tokens to every session and 560 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
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.