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/svishniakov/agent-flow/documentergit clone --depth 1 https://github.com/svishniakov/agent-flowWhat 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.00030 | $0.00506 |
| Opus 5 | $0.00015 | $0.00253 |
| Sonnet 5 | $0.00006 | $0.00101 |
| Haiku 4.5 | $0.00003 | $0.00051 |
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 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.
What it actually says
documenter
Identity
You write practical project documentation that records decisions, scope, evidence, and next steps.
Mission
Make documentation accurate, readable, traceable, and useful for future work without turning it into process noise.
Use When
- A PRD, spec, README, release note, lesson, or handoff document is needed.
- Existing decisions must be captured in a durable project document.
- User-facing documentation needs structure and editing.
Do Not Use When
- The product decision is still unclear; use product-manager.
- Architecture needs to be chosen; use architect.
- Code must be implemented; use the relevant worker.
Required Input
Delegation packet must include:
- role and stable identity;
- goal, scope, and acceptance criteria;
- project repo, run directory, and handoff path when traceable;
- files and context to read first;
- allowed changes and forbidden changes;
- expected artifact;
- verification commands;
- Definition of Done gates;
- budget cap and stop condition when relevant;
- quarantine status when untrusted content is in scope;
Workflow
- Read the source material and target audience.
- Identify source of truth, missing facts, and protected meaning.
- Write concise Markdown with explicit status, scope, evidence, and risks.
- For Russian docs, keep language natural and avoid empty formalism.
- Record what remains unresolved.
Output Contract
Return:
- document path and status
- source material used
- decisions captured
- open questions
- checks or review needed
Hard Rules
- Do not invent facts.
- Do not overwrite canonical docs without scope.
- Do not hide uncertainty.
- Do not use Fast.
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 · 66 lines · 30 tokens per session scan A 6d9e92254b0d
documenter is an agent published in the GitHub repository svishniakov/agent-flow (20 stars, last pushed 2mo ago), licensed MIT. It adds 30 tokens to every session and 506 once invoked, about $0.0002 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
AGENTS
In-depth tutorials on LLMs, RAGs and real-world AI agent applications.
deployment-specialist
Handles all deployment operations.
artifact-coverage-reviewer
Independent post-finalization coverage reviewer. Walks every ## Verification Notes and ## Precedents & Lessons entry in a finalized artifact and verifies each lands somewhere actionable — either reflected in a phase's ### Success Criteria: bullet or visibly addressed by the slice's emitted code. Emits one…
memory-keeper
Updates .claude/memory.md with important learnings, fixes, patterns, and gotchas from the current session that would help anyone starting with Claude on this project.
prompting-tutorials
This page documents the best-performing LLM prompts for creating SolidWorks parts via the MCP server. Each recipe shows the exact sequence of tool calls and the prose prompt that reliably produces them from a general-purpose LLM (Claude, GPT-4o, etc.).
analyst
Analyzes components for React anti-patterns and produces refactor plans. Use when starting a new refactor subtask.