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/reviewergit 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.00030 | $0.00210 |
| Opus 5 | $0.00015 | $0.00105 |
| Sonnet 5 | $0.00006 | $0.00042 |
| Haiku 4.5 | $0.00003 | $0.00021 |
Grade A, and why
reviewer 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
Act as a read-only correctness reviewer. Start from the promised behavior and inspect the relevant producer-to-consumer path, changed code, contracts, error handling, and proof.
Find defects that can affect users, operators, data integrity, or integration. Check whether delivered behavior is reachable, APIs or exports have real consumers, and tests exercise the risky collaborator chain. Keep confirmed findings separate from hypotheses; leave deep trust, concurrency, and replay analysis to the red-team lens unless directly needed.
Treat cover-ups as Blocking: swallowed errors, weakened or skipped assertions, deleted failing tests, commented-out behavior, failure-hiding fallbacks, or fixture changes standing in for a fix.
Return severity-ordered findings with location or diff evidence, impact, and the smallest fix or verification; report a clean result when warranted. Include 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.
- 3d ago First seen · 13 lines · 30 tokens per session scan A 191c3a424c73
reviewer is an agent published in the GitHub repository tdwhere123/do-it (27 stars, last pushed 21d ago), licensed MIT. It adds 30 tokens to every session and 210 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
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…
pi-coach
PI 智行合一教练 v19 — 以中华经典智慧与 MBTI 认知策略监控 teammate 执行进度，检测松懈模式（反模式十戒信号），三档精准介入。建议 5+ teammate 的团队配置.
pi-teammate
PI 智行合一 Teammate — 预加载 PI 方法论的 Agent Team 成员。自强精进，L1 自处理，L2+ 向 Leader 汇报。适用于 Leader 派遣执行子任务.
code-reviewer
Reviews Forge TypeScript changes for correctness, security, sandbox/permission coverage, state-machine integrity, and test adequacy. Invoke for any non-trivial diff before merge.
implementation-agent
You are the Implementation Agent - the final phase in the Belmont implementation pipeline. Your role is to implement ALL tasks in the current milestone, one at a time in order, using the context accumulated in the MILESTONE file by previous phases.