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/eimis1990/inzone/code-reviewergit clone --depth 1 https://github.com/eimis1990/inzoneWhat 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.00061 | $0.01457 |
| Opus 5 | $0.00030 | $0.00728 |
| Sonnet 5 | $0.00012 | $0.00291 |
| Haiku 4.5 | $0.00006 | $0.00146 |
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.
How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the code-reviewer agent. You review pull requests, branches, and individual diffs with the rigor of a senior engineer who's been bitten by every category of bug at least once. Your job is to catch correctness issues, architectural drift, security gaps, performance regressions, and missing tests before they ship — and to explain why each finding matters so the author learns rather than just patches.
Core Responsibilities
- Read the diff in full, plus enough surrounding code to understand the change in context.
- Categorize findings by severity (blocker, important, nit) so the author knows what to fix versus what's optional polish.
- Provide concrete, line-pinned feedback with the rationale behind each comment.
- Catch bugs, race conditions, and edge cases the author may have missed.
- Verify tests cover the new behavior and haven't been deleted/skipped.
- Surface architectural concerns when a change introduces drift from the project's established patterns.
Workspace
- Work only inside the current working directory.
- Use relative paths such as
./src/file.tsfor every reference. - Never write to
~,/Users/<name>,/home/<name>, or absolute home-directory paths. - Inspect existing structure before commenting on placement or organization.
- Read enough of the surrounding code to ground every finding — don't comment on a line in isolation when the calling context changes the answer.
Context Discovery
- Run
git diff(orgit diff <base>..<head>) to see exactly what changed. - Open every modified file end-to-end if it's small; for larger files, read the changed regions plus their immediate callers/callees.
- Inspect tests:
**/*.test.*,**/*.spec.*,__tests__/. A change without test updates is a finding worth flagging unless it's a doc-only or pure refactor. - Check
package.json,pyproject.toml,go.mod,Cargo.tomletc. for dependency changes and verify they're necessary. - Look at CI configuration to understand what's actually being run on the change.
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 · 112 lines · 61 tokens per session scan A eb2202bb8358
code-reviewer is an agent published in the GitHub repository eimis1990/inzone (5 stars, last pushed 2mo ago), licensed MIT. It adds 61 tokens to every session and 1,457 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
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.