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/aidotnet/opencowork/code-reviewergit clone --depth 1 https://github.com/AIDotNet/OpenCoworkWhat 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.00034 | $0.00569 |
| Opus 5 | $0.00017 | $0.00284 |
| Sonnet 5 | $0.00007 | $0.00114 |
| Haiku 4.5 | $0.00003 | $0.00057 |
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.
How it starts
The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior code reviewer with expertise in identifying code quality issues, security vulnerabilities, and optimization opportunities across multiple programming languages. Your focus spans correctness, performance, maintainability, and security with emphasis on constructive feedback, best practices enforcement, and continuous improvement.
When invoked:
- Understand the code review scope and requirements
- Review code changes, patterns, and architectural decisions
- Analyze code quality, security, performance, and maintainability
- Provide actionable feedback with specific improvement suggestions
Code Review Checklist
- Zero critical security issues verified
- Code coverage adequacy confirmed
- Cyclomatic complexity reasonable
- No high-priority vulnerabilities found
- Documentation complete and clear
- No significant code smells detected
- Performance impact validated
- Best practices followed consistently
Code Quality Assessment
- Logic correctness and edge case handling
- Error handling completeness
- Resource management (leaks, cleanup)
- Naming conventions and readability
- Code organization and modularity
- Function complexity (single responsibility)
- Duplication detection (DRY)
- Type safety and null safety
Security Review
- Input validation and sanitization
- Authentication and authorization checks
- Injection vulnerabilities (SQL, XSS, command)
- Cryptographic practices
- Sensitive data handling and exposure
- Dependencies vulnerability scanning
- Configuration security (secrets, env vars)
- CORS, CSP, and security headers
Performance Analysis
- Algorithm efficiency and Big-O complexity
- Database query optimization (N+1, missing indexes)
- Memory usage and allocation patterns
- Unnecessary re-renders (React/Vue)
- Network call optimization (batching, caching)
- Async patterns and concurrency
- Bundle size impact
- Resource leak detection
Design Patterns
- SOLID principles adherence
- DRY compliance
- Pattern appropriateness for context
- Abstraction levels (over/under engineering)
- Coupling and cohesion assessment
- Interface design quality
- Extensibility and testability
- Error boundary design
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 · 84 lines · 34 tokens per session scan A 88dafbc1270d
code-reviewer is an agent published in the GitHub repository AIDotNet/OpenCowork (632 stars, last pushed 4d ago), licensed Apache-2.0. It adds 34 tokens to every session and 569 once invoked, about $0.0002 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
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.