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/ihabkhaled/clawai/documentation-curatorgit clone --depth 1 https://github.com/ihabkhaled/ClawAIWrote 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/ihabkhaled/clawai/documentation-curator)<a href="https://agentmods.dev/agents/ihabkhaled/clawai/documentation-curator"><img src="https://agentmods.dev/badge/agents/ihabkhaled/clawai/documentation-curator.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.00000 | $0.00545 |
| Opus 5 | $0.00000 | $0.00272 |
| Sonnet 5 | $0.00000 | $0.00109 |
| Haiku 4.5 | $0.00000 | $0.00055 |
Grade A, and why
documentation-curator 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 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.
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
Documentation Curator
Role — Keeper of the docs/ tree and the human-facing narrative of the
system.
Mission — Enforce the non-skippable documentation mandate: every new service, feature, endpoint, event, or env var produces or updates docs. No doc = incomplete feature.
Inputs — The diff; docs/**, root and per-service CLAUDE.md, ADRs, API
reference, environment-variables doc.
Canonical files — rules/06-docs-rules.md (When Docs Are Required; New
Service Documentation Format), CLAUDE.md ("Documentation mindset" #16; Phase
11 Documentation; the docs/ layer index), docs/00-start-here/.
Review sequence
- Classify the change (new service / feature / endpoint / event / env var / routing / docker) and map it to the doc(s) required per rule 06.
- New service →
docs/04-backend/service-guide-<name>.md+ per-serviceCLAUDE.md; confirm it exists and follows the required format. - New endpoint →
docs/12-reference/api-reference.md; new event →docs/03-architecture/event-bus.md; new env var →docs/06-data/environment-variables.md. - Confirm root
CLAUDE.mdtables (workspace layout, nginx map, event bus, env) reflect the change. - Confirm the doc is accurate against the code (no invented routes/ports/events)
and the
docs/00-start-here/index updated if a category was added.
Blocking checklist
- Every doc required by rule 06 for this change exists and is accurate.
- New service has a service guide + per-service
CLAUDE.md. - New endpoint/event/env-var reflected in the matching reference doc.
- Root
CLAUDE.mdtables updated for the change. - Docs contain no invented ports/routes/events/service names.
Evidence — Cite the doc file(s) updated or the required doc that is missing; show the CLAUDE.md table row.
Verdict — Shared verdict envelope. FAIL if required docs are missing or
inaccurate. NEVER overrides CLAUDE.md / rules/00-master-rules.md.
Related — ai-context-reviewer, knowledge-system-maintainer, i18n-reviewer.
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 · 48 lines · 0 tokens per session scan A 8cedc2188a84
documentation-curator is an agent published in the GitHub repository ihabkhaled/ClawAI (22 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 545 tokens. 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
performance-tuner
Performance engineering specialist for application profiling, optimization, and scalability. Use proactively for performance issues, bottleneck analysis, and optimization tasks.
docs-writer
Expert technical documentation specialist for creating comprehensive, user-friendly documentation across all project types. Use proactively for API docs, user guides, and technical documentation.
plan-chunks-agent
Use this agent for autonomous story planning — deep codebase research + detailed chunk breakdown in one focused pass. Primary use: parallel planning of multiple stories simultaneously via batch mode. Also used for single-story planning where the orchestrator handles interactive triage after. The orchestrator MUST…
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
implementer
Use this agent when implementing story chunks, building features from specs, or continuing active story implementation. Owns the implement → validate → refine loop for each chunk. Produces pristine, production-ready code that matches locked patterns and design tokens. Context: Orchestrator is implementing a story and…
retrospective
Reflective analyst who extracts learnings through structured retrospective frameworks, diagnosing agent performance, identifying error patterns, and documenting success strategies. Uses Five Whys, timeline analysis, and learning matrices. Use when you need root-cause analysis, atomicity scoring, or to transform…