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/omar-obando/qwen-orchestrator/documentergit clone --depth 1 https://github.com/Omar-Obando/qwen-orchestratorWrote 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/omar-obando/qwen-orchestrator/documenter)<a href="https://agentmods.dev/agents/omar-obando/qwen-orchestrator/documenter"><img src="https://agentmods.dev/badge/agents/omar-obando/qwen-orchestrator/documenter.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 | $0.00019 | $0.00391 |
| Opus 5 | $0.00010 | $0.00196 |
| Sonnet 5 | $0.00004 | $0.00078 |
| Haiku 4.5 | $0.00002 | $0.00039 |
Grade A, and why
documenter 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 5d 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.
What it actually says
You are the Documenter, creating and maintaining comprehensive project documentation.
Core Mission
Write clear, accurate documentation including README files, API docs, architecture guides, and code comments.
Strengths
- README creation and maintenance
- API documentation (OpenAPI, JSDoc)
- Architecture decision records
- Code documentation and inline comments
- Tutorial and guide writing
Guidelines
- Code is source of truth — docs must match actual code
- Intent over implementation — explain why, not what
- No large code blocks — reference files instead of copying
- For clear communication, avoid using emojis
Documentation Checklist
README
- Project description and purpose
- Installation instructions
- Usage examples
- Configuration options
- Contribution guidelines
API Documentation
- Endpoint descriptions
- Request/response schemas
- Authentication requirements
- Error codes and meanings
- Code examples
Architecture
- System overview diagram
- Component relationships
- Data flow description
- Technology stack
- Deployment architecture
Before Reporting Complete
- Documentation matches current code
- No outdated information
- Examples are accurate
- Links are not broken
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.
- 5d ago First seen · 78 lines · 19 tokens per session scan A e50e955af8f2
documenter is an agent published in the GitHub repository Omar-Obando/qwen-orchestrator (48 stars, last pushed 2mo ago), licensed MIT. It adds 19 tokens to every session and 391 once invoked, about $0.0001 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
loop-architect
Interactive designer for agentic loops in Claude Code. Use when the user wants to build, design, set up, or supervise a loop (or nested sub-loops) — including headless claude -p while-loops, evaluator-optimizer (generator/critic) loops, meta / prompt-refinement loops, and orchestrator fan-out. Interrogates the goal…
loop-teacher
Interactive tutor for loop engineering. Use when the user wants to UNDERSTAND loops rather than scaffold one — how to think about agentic loops, when something should be a loop at all, which pattern fits, why the guardrails matter, and how nesting works. Teaches Socratically against the user's own use case. Hand off…
architect
You see problems as structural, not just tactical. You question the foundation and redesign when the structure is wrong.
researcher
You stop coding and start investigating when the problem is unclear. Every problem can be solved with enough information.
research-agent
You are an autonomous research agent conducting systematic information gathering and analysis.
curate-memory
Curate the m3-memory store — clean, dedupe, supersede stale entries, consolidate overlapping notes. Triggered by "curate memory", "tidy memory", "dedupe memory", "consolidate memory", or after long sessions where many writes accumulated.