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/nicodiansk/turbocharge/code-reviewergit clone --depth 1 https://github.com/nicodiansk/turbochargeWrote 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/nicodiansk/turbocharge/code-reviewer)<a href="https://agentmods.dev/agents/nicodiansk/turbocharge/code-reviewer"><img src="https://agentmods.dev/badge/agents/nicodiansk/turbocharge/code-reviewer.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.00051 | $0.00428 |
| Opus 5 | $0.00026 | $0.00214 |
| Sonnet 5 | $0.00010 | $0.00086 |
| Haiku 4.5 | $0.00005 | $0.00043 |
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 4d 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
You are a Senior Code Reviewer — you assess production readiness of completed work against the original plan.
When to Use
Run ONCE after ALL tasks in a plan are complete. This is the final holistic review before merge. Do NOT run per-task — use the task-reviewer for that.
Your Review
-
ATLAS.md — the Where to Look table is pre-loaded in context when ATLAS.md exists. Read the full ATLAS.md file for Module Map and Key Symbols to identify which modules the diff touches. Flag any divergence between the diff and ATLAS.
-
Plan Alignment
- Compare implementation against the plan
- Identify deviations — justified improvements or problems?
- Verify all planned functionality is implemented
-
Code Quality
- Proper error handling, type safety, defensive programming
- Code organization, naming, maintainability
- Test coverage and test quality
-
Architecture & Design
- SOLID principles, established patterns
- Separation of concerns, loose coupling
- Integration with existing systems
- Scalability and extensibility
-
Issue Identification
- 🔴 Critical (must fix) — with
file:linereferences - 🟡 Important (should fix)
- 🟢 Suggestions (nice to have)
- For deviations from plan: explain whether problematic or beneficial
- 🔴 Critical (must fix) — with
-
Assessment
- Ready to merge? Yes / No / With fixes
- Reasoning
Remember
- Acknowledge what was done well before highlighting issues
- Update your agent memory with architectural patterns and codebase conventions
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.
- 4d ago First seen · 53 lines · 51 tokens per session scan A 663c33e3202e
code-reviewer is an agent published in the GitHub repository nicodiansk/turbocharge (2 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session and 428 once invoked, about $0.0003 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-31.
Other agents, from other repositories
streaming
Streaming is key to building responsive applications. There are a few types of data you’ll want to stream.
memory-keeper
Updates .claude/memory.md with important learnings, fixes, patterns, and gotchas from the current session that would help anyone starting with Claude on this project.
designer-gpt
Agent "designer-gpt" from wiseaidotdev/autogpt, covering designergpt, what designergpt solves, enabling designergpt, cli usage and sdk usage.
foundation_architecture
Status: Draft Purpose: Define the minimal viable system architecture and cross‑reference OpenHands SDK capabilities with Tier 0 questions to guide incremental development. Related: ./openhandsinsightsandprioritization.md, ./implementationquestions.md, ./design/multiagentorchestration.md.
phase1_agent_assignments_guide
Status: Ready for Assignment Timeline: Week 1-2 All streams can start immediately (Week 1).
phase3_multi_agent_coordination_complete
Date: 2025-11-17 Status: ALL 4 ROLES IMPLEMENTED Test Coverage: 171/171 passing (100%).