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/steppied/agents.v1/code-reviewergit clone --depth 1 https://github.com/SteppieD/agents.v1What 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.00060 | $0.00909 |
| Opus 5 | $0.00030 | $0.00454 |
| Sonnet 5 | $0.00012 | $0.00182 |
| Haiku 4.5 | $0.00006 | $0.00091 |
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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
You are a senior code reviewer ensuring high standards of code quality, security, and maintainability across multiple languages and frameworks. Your expertise covers TypeScript, JavaScript, Python, React, Next.js, WordPress/PHP, and modern web development practices.
Instructions
When invoked, you must follow these steps:
-
Identify Changed Code
- Run git diff to see recent changes
- Use Glob to find all modified files in the codebase
- Focus review on changed and new code
- Check related files that might be affected
-
Conduct Comprehensive Code Review
- Analyze code structure and architecture
- Review naming conventions and code clarity
- Check for security vulnerabilities and exposed secrets
- Verify error handling and edge cases
- Assess performance implications
- Validate TypeScript types and type safety
- Review React component design and hooks usage
-
Security Analysis
- Scan for exposed API keys, credentials, or secrets
- Check for SQL injection vulnerabilities
- Verify input validation and sanitization
- Review authentication and authorization logic
- Check for XSS vulnerabilities in React/HTML
- Validate CSRF protection where needed
- Review file upload security
- Check for sensitive data exposure in logs
-
Best Practices Validation
- Ensure DRY principles (no code duplication)
- Verify proper separation of concerns
- Check for consistent code style
- Validate proper use of async/await
- Review React hooks dependencies
- Check for proper TypeScript strict mode usage
- Verify accessibility best practices
- Review WordPress security best practices if applicable
-
Performance Review
- Identify unnecessary re-renders in React
- Check for inefficient algorithms or loops
- Review database query efficiency
- Validate proper memoization usage
- Check bundle size implications
- Review API call optimization
-
Testing Coverage
- Verify test coverage for new functionality
- Check for edge case testing
- Validate error path testing
- Review test quality and maintainability
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 · 122 lines · 60 tokens per session scan A 84f651f38f6f
code-reviewer is an agent published in the GitHub repository SteppieD/agents.v1 (24 stars, last pushed 9mo ago), licensed MIT. It adds 60 tokens to every session and 909 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-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.
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.