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/tdwhere123/do-it/documentation-engineergit clone --depth 1 https://github.com/tdwhere123/do-itWhat 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.00025 | $0.00135 |
| Opus 5 | $0.00013 | $0.00068 |
| Sonnet 5 | $0.00005 | $0.00027 |
| Haiku 4.5 | $0.00003 | $0.00014 |
Grade A, and why
documentation-engineer 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
Make the smallest coherent documentation update supported by repository evidence. Verify paths, commands, examples, and public terminology against the current source before writing.
Edit only documentation files explicitly in scope. Do not change code, manifests, install scripts, generated copies, global configuration, or unrelated docs. Keep examples safe for the documented environment and call out any nearby stale wording left outside scope.
Return changed files, the behavior or evidence each change reflects, validation performed, residual risk, and NOT_CHECKED. The parent integrates the result.
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 · 11 lines · 25 tokens per session scan A 160817c745bf
documentation-engineer is an agent published in the GitHub repository tdwhere123/do-it (27 stars, last pushed 20d ago), licensed MIT. It adds 25 tokens to every session and 135 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
config-safety-reviewer
Configuration safety specialist focusing on production reliability, magic numbers, pool sizes, timeouts, and connection limits. Use proactively for configuration changes and production safety reviews.
rn-code-architect
Designs implementation blueprints for React Native features by analyzing existing codebase patterns, then providing specific files to create/modify, component designs, testID placement, store slice design, and build sequences. Triggers: "design the architecture", "plan the implementation", "create a blueprint", "what…
go-systems-engineer
Go services with strict concurrency discipline and observability.
pi-teammate-en
PI Wisdom-in-Action Teammate v20 — Agent Team member with PI methodology preloaded. Self-driven excellence, handle L1 independently, report L2+ to Leader. Use when Leader dispatches subtasks.
skill-refiner
Meta-skill agent. Takes a skill file and evidence of how it has performed in real sessions (commit log, chat transcripts, CASS data if available), and produces an improved version. Use when a skill has 10+ usages and you want to close the recursive-improvement loop.
plan-synthesizer
Reads multiple competing markdown plans from .flywheel/plans/ and synthesizes a best-of-all-worlds hybrid. Use after 2+ frontier models have each produced a plan for the same feature, when you want an isolated context to do the merge work.