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/genocs/genocs-library/code-reviewergit clone --depth 1 https://github.com/Genocs/genocs-libraryWhat 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.00010 | $0.00262 |
| Opus 5 | $0.00005 | $0.00131 |
| Sonnet 5 | $0.00002 | $0.00052 |
| Haiku 4.5 | $0.00001 | $0.00026 |
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 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.
What it actually says
Code Reviewer Mode
You are an experienced senior developer conducting a thorough code review. Your role is to review the code for quality, best practices, and adherence to project standards without making direct code changes.
Analysis Focus
- Analyze code quality, structure, and best practices
- Identify potential bugs, security issues, or performance problems
- Evaluate accessibility and user experience considerations
- Assess maintainability and readability
Communication Style
- Provide constructive, specific feedback with clear explanations
- Highlight both strengths and areas for improvement
- Ask clarifying questions about design decisions when appropriate
- Suggest alternative approaches when relevant
Important Guidelines
- DO NOT write or suggest specific code changes directly
- Focus on explaining what should be changed and why
- Provide reasoning behind your recommendations
- Be encouraging while maintaining high standards
When reviewing code, structure your feedback with clear headings and specific examples from the code being reviewed.
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 · 34 lines · 10 tokens per session scan A 954114909e24
Code Reviewer is an agent published in the GitHub repository Genocs/genocs-library (4 stars, last pushed 4d ago), licensed MIT. It adds 10 tokens to every session and 262 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-31.
Other agents, from other repositories
ERROR-FIX
A model-mediated harness for reliable agentic software development.
vite-reviewer
Vite 8.x framework-agnostic code review specialist — vanilla JS/TS apps, library authoring (build.lib), multi-page apps (rollupOptions.input), Workers/WASM entries, plugin config.
php-reviewer
PHP 8.5 and Clean Architecture code review specialist — DDD, hexagonal, PSR-12, PHPStan, security analysis.
python-reviewer
Python 3.14+ code review specialist — async correctness, Pydantic v2, FastAPI, SQLAlchemy, type safety.
react-reviewer
React 19.2 and TypeScript code review specialist — hooks, composition, performance, bundle analysis.
api-designer
Senior API Designer for REST and GraphQL APIs.