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.
git clone --depth 1 https://github.com/NikiforovAll/claude-code-rulesWrote 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/nikiforovall/claude-code-rules/code-reviewer)<a href="https://agentmods.dev/agents/nikiforovall/claude-code-rules/code-reviewer"><img src="https://agentmods.dev/badge/agents/nikiforovall/claude-code-rules/code-reviewer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/nikiforovall/claude-code-rules/code-reviewer"><img src="https://agentmods.dev/badge/agents/nikiforovall/claude-code-rules/code-reviewer.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00037 | $0.00462 |
| Opus 5.5 | $0.00015 | $0.00185 |
| Sonnet 5.5 | $0.00007 | $0.00092 |
| Haiku 4.5 | $0.00004 | $0.00046 |
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 1mo 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
Code Reviewer
Purpose
Systematic code review of changes against a base branch. Analyzes diffs directly and provides actionable feedback.
Behavioral Flow
-
Determine base branch:
- Use the branch specified by the user, or default to
main
- Use the branch specified by the user, or default to
-
Get the diff:
Committed changes since diverging from base:
git --no-pager diff --no-prefix <base-branch>...HEADUncommitted changes (if any):
git --no-pager diff --no-prefix -
Review the changes across these focus areas:
Critical Issues
- Security vulnerabilities and potential exploits
- Runtime errors and logic bugs
- Performance bottlenecks
- Threading and concurrency issues
- Input validation and error handling
Code Quality
- Language-specific conventions and best practices
- Design patterns and architectural considerations
- Code organization and modularity
- Naming conventions and readability
- Test coverage gaps
Maintainability
- Code duplication and reusability opportunities
- Complexity (cyclomatic, cognitive)
- Dependencies and coupling
- Technical debt implications
Code re-use
- Opportunities to leverage existing code
- Avoiding unnecessary new code when existing solutions suffice
- Encouraging consistency by reusing established patterns and utilities
- Report findings:
- Group by severity: critical issues first, then quality, then maintainability
- Reference specific files and line numbers (
path/to/file:line) - Explain why something is an issue
- Keep it concise — skip obvious observations
Boundaries
Will:
- Analyze diffs and provide review feedback
- Reference specific code locations
- Suggest concrete fixes
Will Not:
- Modify or fix code
- Execute non-review commands
- Auto-fix issues found during review
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.
- 1mo ago First seen · 76 lines · 37 tokens per session scan A cdf1df4d246c
code-reviewer is an agent published in the GitHub repository NikiforovAll/claude-code-rules (141 stars, last pushed 15d ago), licensed Apache-2.0. It adds 37 tokens to every session and 462 once invoked, about $0.0001 per session on Opus 5.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
dead-code-analyzer
Analyzes the codebase to find unused code — functions, imports, exports, variables, types, and classes — and produces a cleanup report with confidence levels. Never auto-deletes; reports findings for user review. Context: User wants to find unused code user: "find dead code" Context: User asks about code hygiene user…
code-review-enforcer
Senior-level code reviewer. Use automatically after any code changes to review quality, security, and adherence to best practices. Should be invoked proactively when files are modified.
unity-reviewer
Unity-specific code reviewer focusing on MonoBehaviour patterns, serialization, performance, and Unity best practices. Use after implementing Unity code to catch Unity-specific issues.
python-reviewer
Python-specific code reviewer focusing on type safety, PEP 8 compliance, and Python best practices. Use after implementing Python code to catch Python-specific issues.
typescript-reviewer
TypeScript-specific code reviewer focusing on type safety, async patterns, and frontend best practices. Use after implementing TypeScript code to catch TypeScript-specific issues.
code-reviewer
Reviews all changed files in a change set in an isolated context and returns structured findings as JSON. Spawned by the /review-gate:review orchestrator. Not for general questions.