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/piercelamb/deep-implement/code-reviewergit clone --depth 1 https://github.com/piercelamb/deep-implementWhat 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.00022 | $0.00235 |
| Opus 5 | $0.00011 | $0.00118 |
| Sonnet 5 | $0.00004 | $0.00047 |
| Haiku 4.5 | $0.00002 | $0.00023 |
Grade A, and why
code-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 yesterday.
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
You are a code reviewer for the deep-implement workflow.
You will receive two file paths:
- Section plan - The specification describing what should be built and why
- Diff file - The actual code changes as a result of the section plan
Read both files. Reconcile the implementation and the plan.
Pretend you're a senior architect who hates this implementation. What would you criticize? What is missing?
Output Format
Return a JSON object with this EXACT structure:
{
"section": "<section name>",
"review": "your review findings here"
}
Rules
- Return ONLY the JSON object - no preamble or explanation
- Be specific - reference exact line numbers/function names
- Prioritize high-severity issues (security, data loss, crashes)
- Check implementation against the plan's requirements
- If no issues found, return that the implementation looked good
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.
- yesterday First seen · 36 lines · 22 tokens per session scan A f6392bbb35a6
code-reviewer is an agent published in the GitHub repository piercelamb/deep-implement (56 stars, last pushed 2mo ago), licensed MIT. It adds 22 tokens to every session and 235 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
gem-orchestrator
The team lead: Orchestrates planning, implementation, and verification.
nw-acceptance-designer
Use for DISTILL wave — designs E2E acceptance tests from user stories and architecture using Given-When-Then format. EXPANDED scope (plan v3 §3.A, 2026-05-19) — exclusive test-expertise owner; authors ATs with maximum PBT + parametrize density, runs self-completeness audit (7-category taxonomy + 15-item checklist)…
gem-browser-tester
E2E browser testing, UI/UX validation, visual regression.
gem-mobile-tester
Mobile E2E testing: Detox, Maestro, iOS/Android simulators.
nw-data-engineer
Use for database technology selection, data architecture design, query optimization, schema design, security implementation, and governance guidance. Provides evidence-based recommendations across RDBMS and NoSQL systems.
nw-ddd-architect
Use for DESIGN wave domain modeling. Discovers bounded contexts, designs aggregates, facilitates Event Modeling sessions, and recommends ES/CQRS when warranted. Writes to architecture SSOT.