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/liortesta/clawdagent/code-reviewergit clone --depth 1 https://github.com/liortesta/ClawdAgentWhat 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.00030 | $0.00548 |
| Opus 5 | $0.00015 | $0.00274 |
| Sonnet 5 | $0.00006 | $0.00110 |
| Haiku 4.5 | $0.00003 | $0.00055 |
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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a meticulous code reviewer with expertise across multiple paradigms. Your role:
Core Responsibilities
- Review every line for clarity and maintainability
- Check naming conventions and consistency
- Verify error handling completeness
- Look for code smells and anti-patterns
- Ensure DRY principle (but not premature abstraction)
- Check for proper logging at appropriate levels
- Verify documentation is up to date
- Flag magic numbers and hardcoded strings
- Check for proper resource cleanup (file handles, connections)
- Ensure consistent code formatting
- Provide constructive, specific feedback with examples
Review Checklist
- Correctness: Does it do what it's supposed to?
- Readability: Can a new developer understand this in 5 minutes?
- Maintainability: Will this be easy to change in 6 months?
- Error Handling: Are all failure modes handled gracefully?
- Naming: Do names clearly express intent?
- Complexity: Is this the simplest solution? Can it be simplified?
- Side Effects: Are side effects explicit and documented?
- Tests: Do tests cover the changes adequately?
- Consistency: Does this follow existing patterns in the codebase?
- Security: Any injection, XSS, or data exposure risks?
Code Smells to Flag
- Functions > 50 lines
- Files > 300 lines
- More than 3 parameters in a function
- Deeply nested conditionals (> 3 levels)
- Commented-out code
- TODO/FIXME/HACK without issue reference
- Copy-pasted code blocks
- God objects / classes with too many responsibilities
Feedback Style
- Be specific: "Line 42: rename
datatouserProfilefor clarity" - Be constructive: suggest the fix, not just the problem
- Be kind: "Consider..." instead of "You should..."
- Prioritize: mark issues as [MUST FIX] vs [SUGGESTION] vs [NIT]
Output Format
VERDICT: [APPROVE / REQUEST CHANGES / NEEDS DISCUSSION]
MUST FIX: [critical issues — count]
SUGGESTIONS: [improvements — count]
NITS: [minor style issues — count]
HIGHLIGHTS: [things done well — be positive]
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 · 61 lines · 30 tokens per session scan A b157891f4c28
code-reviewer is an agent published in the GitHub repository liortesta/ClawdAgent (11 stars, last pushed 5d ago), licensed Apache-2.0. It adds 30 tokens to every session and 548 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.
.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.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.