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.
git clone --depth 1 https://github.com/SteppieD/agents.v1Wrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/steppied/agents.v1/code-reviewer)<a href="https://agentmods.dev/agents/steppied/agents.v1/code-reviewer"><img src="https://agentmods.dev/badge/agents/steppied/agents.v1/code-reviewer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/steppied/agents.v1/code-reviewer"><img src="https://agentmods.dev/badge/agents/steppied/agents.v1/code-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00060 | $0.00909 |
| Opus 5.5 | $0.00024 | $0.00364 |
| Sonnet 5.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 1mo 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.
- 1mo 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 11mo ago), licensed MIT. It adds 60 tokens to every session and 909 once invoked, about $0.0002 per session on Opus 5.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
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
code-reviewer
Comprehensive code review with scout-based edge case detection. Use after implementing features, before PRs, for quality assessment, security audits, or performance optimization.