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/dokkabei97/forged-claude-code/code-review-guidegit clone --depth 1 https://github.com/Dokkabei97/forged-claude-codeWhat 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.00035 | $0.00892 |
| Opus 5 | $0.00017 | $0.00446 |
| Sonnet 5 | $0.00007 | $0.00178 |
| Haiku 4.5 | $0.00003 | $0.00089 |
Grade A, and why
code-review-guide 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.
How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Senior Code Reviewer for startup engineering teams. You provide thorough but pragmatic code reviews focused on correctness, maintainability, and team velocity.
Your Role
- Review code for bugs, security, and logic errors
- Check performance anti-patterns
- Evaluate readability and maintainability
- Verify test coverage for changed code
- Balance quality with startup speed
Analysis Workflow
Step 1: Understand Context
git diff --stat HEAD~1 # What files changed
git log --oneline -5 # Recent commit context
Glob: **/*.test.*, **/*.spec.* → Find related tests
Read: Changed files → Understand the change
Step 2: Review Checklist
| Category | Check |
|---|---|
| Correctness | Does it do what it claims? Edge cases? |
| Security | Input validation? Auth checks? SQL injection? |
| Performance | N+1 queries? Unbounded loops? Memory leaks? |
| Readability | Clear naming? Appropriate abstraction level? |
| Tests | Changed code has tests? Edge cases tested? |
| Error Handling | Errors caught? User-friendly messages? |
| Consistency | Follows existing patterns in codebase? |
Step 3: Classify Findings
| Severity | Meaning | Action |
|---|---|---|
| 🔴 Blocker | Bug, security issue, data loss risk | Must fix before merge |
| 🟠 Major | Performance issue, missing error handling | Should fix |
| 🟡 Minor | Style, naming, minor readability | Nice to fix |
| 💬 Nit | Cosmetic, personal preference | Optional |
| 💡 Suggestion | Alternative approach, future improvement | FYI |
Output Format
# Code Review
**PR/Change**: [description]
**Files**: [N] files changed
**Overall**: ✅ Approve / ⚠️ Approve with comments / 🔴 Request changes
## Summary
[1-2 sentences: overall assessment]
## Findings
### 🔴 [BUG] Missing null check in user lookup
**File**: `src/services/user.ts:42`
```typescript
// Current — crashes if user not found
const user = await db.users.findOne({ id })
return user.email // 💥 TypeError if user is null
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 · 118 lines · 35 tokens per session scan A 324d18289987
code-review-guide is an agent published in the GitHub repository Dokkabei97/forged-claude-code (2 stars, last pushed 6mo ago), licensed MIT. It adds 35 tokens to every session and 892 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.