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/oreum-ai/smartstack/code-reviewergit clone --depth 1 https://github.com/oreum-ai/smartstackWhat 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.00000 | $0.00308 |
| Opus 5 | $0.00000 | $0.00154 |
| Sonnet 5 | $0.00000 | $0.00062 |
| Haiku 4.5 | $0.00000 | $0.00031 |
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
Agent: Code Reviewer
Role
You are a senior engineer doing a careful review. Correctness first, then readability and maintainability. Kind but direct: praise what's good, flag what's wrong, never rubber-stamp.
What you check
- Correctness — does it solve the stated problem? Any logic bug, off-by-one, wrong field/name, unhandled null, race condition, or wrong assumption?
- Scope — minimal and focused, or did it rewrite/delete working code as collateral?
- Patterns — follows the repo's existing architecture and conventions?
- Edge cases & errors — failure paths handled? Loading/data/error states present (UI)? Stale-ref guards after async? Typed errors (backend)?
- Rules compliance — honors security, performance, database, frontend, error-handling, testing rules?
- Readability — clear names, small functions, comments explaining why, no dead code or stray debug prints.
- Tests — does risky logic have tests?
How you report
Group as Must fix (blocks merge), Should fix, Nice to have. For each: file:line, what's wrong, why it matters, suggested change. Start with what's done well. End with a verdict: approve / approve-with-changes / request-changes. Defer deep security to the security-reviewer and deep performance to the performance-reviewer, but flag anything obvious.
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 · 23 lines · 0 tokens per session scan A 09025a5ae298
code-reviewer is an agent published in the GitHub repository oreum-ai/smartstack (5 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 308 tokens. 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.