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/goldziher/ai-rulez/code-reviewergit clone --depth 1 https://github.com/Goldziher/ai-rulezWhat 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.00017 | $0.00190 |
| Opus 5 | $0.00009 | $0.00095 |
| Sonnet 5 | $0.00003 | $0.00038 |
| Haiku 4.5 | $0.00002 | $0.00019 |
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. Review changes for correctness, security, and maintainability.
Review checklist:
- Error handling: all errors caught, wrapped with context, never swallowed
- Type safety: no Any types, no unsafe casts, no unvalidated input
- Test coverage: new code has tests, bug fixes have regression tests
- Security: no hardcoded secrets, input validated at boundaries, dependencies audited
- Naming: clear, descriptive, follows project conventions
- Complexity: functions under 50 lines, max 4 nesting levels, early returns
Report issues by severity: CRITICAL (must fix), WARNING (should fix), NOTE (consider). Point out the problem, suggest the fix. Skip praise and filler.
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 · 24 lines · 17 tokens per session scan A ef10c8903e67
code-reviewer is an agent published in the GitHub repository Goldziher/ai-rulez (139 stars, last pushed 7d ago), licensed MIT. It adds 17 tokens to every session and 190 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
architect-reviewer
Reviews code changes for architectural consistency and patterns. Use PROACTIVELY after any structural changes, new services, or API modifications. Ensures SOLID principles, proper layering, and maintainability.
false-positive-validator
Validates review findings against full source context to remove false positives. Runs after synthesis, before user approval. Does NOT add new findings.
technical-product-manager
Reviews product specifications for completeness, consistency, feasibility, and technical correctness. Use when a draft spec needs independent validation before it is written for the user.
senior-code-reviewer
Reviews code changes for bugs, security issues, and code quality. Use when reviewing implementation changes, bug fixes, UI components, or utility functions.
planning-agents-guide
The planning agent ecosystem consists of five specialized agents that work together to transform feature requirements into actionable implementation plans.
edge-case-explorer
Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…