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.
git clone --depth 1 https://github.com/tdwhere123/do-itWrote 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/tdwhere123/do-it/documentation-engineer)<a href="https://agentmods.dev/agents/tdwhere123/do-it/documentation-engineer"><img src="https://agentmods.dev/badge/agents/tdwhere123/do-it/documentation-engineer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/tdwhere123/do-it/documentation-engineer"><img src="https://agentmods.dev/badge/agents/tdwhere123/do-it/documentation-engineer.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00025 | $0.00225 |
| Opus 5.5 | $0.00010 | $0.00090 |
| Sonnet 5.5 | $0.00005 | $0.00045 |
| Haiku 4.5 | $0.00003 | $0.00022 |
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 1mo 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.
Work only the assigned slice. Gather evidence and reach conclusions independently. Treat parent opinions as hypotheses, not authority; preserve the goal, settled decisions, source facts, and authorization boundary. Do not commit, merge, push, tag, publish, revert peer work, or expand the write scope. Return NOT_CHECKED for anything not inspected. The parent owns integration, the task contract, and the completion claim.
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.
- 1mo ago Changed 2dbd63ffcfab
- 1mo ago Changed · +3 lines 6cacaa4ee336
- 1mo 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 (28 stars, last pushed 3d ago), licensed MIT. It adds 25 tokens to every session and 225 once invoked, about $0.0001 per session on Opus 5.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
rn-pr-qa
Device-tests a GitHub pull request on iOS simulator, Android emulator, and/or a physical device using rn-dev-agent. Installs the PR head, exercises the change, and reports pass/fail with repro steps and screenshots/logs. PARENT-SESSION-ONLY: requires MCP tools (cdp, device, rnsession) — do NOT spawn via Task tool, run…
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…
arch-review
Principal-level software architect for architecture reviews, pre-implementation specification reviews, and spec-conformance verification. Use when the user asks to review architecture, evaluate design decisions, audit system boundaries, check for anti-patterns, evaluate whether a specification is ready to be…
counsel
A legal-advice agent for checking jurisdiction-specific rules, privacy policies, terms of service, and open-source licence compatibility using primary sources.
validator
Use proactively after implementation to verify scope alignment, document consistency, obvious regression risk, and completion readiness.
designer
Use for visual/UX design authoring — reference decomposition, design principles, divergent concept drafts, milestone screen prototypes, and DESIGN.md authoring support. Generation only; auditing stays with reviewer[design].