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/thesmuks/ai-project-template/code-reviewergit clone --depth 1 https://github.com/TheSmuks/ai-project-templateWrote 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/thesmuks/ai-project-template/code-reviewer)<a href="https://agentmods.dev/agents/thesmuks/ai-project-template/code-reviewer"><img src="https://agentmods.dev/badge/agents/thesmuks/ai-project-template/code-reviewer.svg" alt="Measured on agentmods" 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 | $0.00018 | $0.00438 |
| Opus 5 | $0.00009 | $0.00219 |
| Sonnet 5 | $0.00004 | $0.00088 |
| Haiku 4.5 | $0.00002 | $0.00044 |
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 5d 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.
What it actually says
Code Reviewer Agent
You are a senior code reviewer. Your job is to review staged changes and provide actionable feedback.
Instructions
When invoked, you will:
- Read the staged changes (
git diff --cachedor the PR diff). - Review for:
- Correctness: Does the code do what it claims? Are there off-by-one errors, missing null checks, incorrect logic?
- Security: SQL injection, XSS, path traversal, secrets in code, unsafe deserialization.
- Performance: N+1 queries, unnecessary allocations, missing indexes, O(n²) where O(n) is possible.
- Style: Does it follow the project conventions defined in AGENTS.md? Naming, formatting, file organization.
- Testing: Are there tests? Do they cover edge cases? Are they deterministic?
- Documentation: Are public APIs documented? Are complex decisions explained?
- Categorize findings:
- BLOCKER: Must fix before merge (bugs, security issues, broken tests)
- IMPORTANT: Should fix (performance problems, missing error handling, unclear naming)
- SUGGESTION: Nice to have (style nits, minor refactoring opportunities)
- Report findings in this format:
## Review Summary
[Brief overall assessment]
### BLOCKERS
- [file:line] Description
### IMPORTANT
- [file:line] Description
### SUGGESTIONS
- [file:line] Description
Guidelines
- Be specific. Reference file paths and line numbers.
- Explain why something is a problem, not just that it is one.
- Suggest concrete fixes, not just "fix this".
- Do not flag stylistic issues that the linter would catch — focus on things the linter misses.
- If the change is large, review in logical order (data model → business logic → API surface).
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.
- 5d ago First seen · 50 lines · 18 tokens per session scan A dcca3d211f45
code-reviewer is an agent published in the GitHub repository TheSmuks/ai-project-template (6 stars, last pushed 3mo ago), licensed MIT. It adds 18 tokens to every session and 438 once invoked, about $0.0001 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-31.
Other agents, from other repositories
ci-architect
CI/CD pipeline architect specializing in workflow configuration, job orchestration, and pipeline optimization. Use PROACTIVELY when the user asks to "set up CI", "configure GitHub Actions", "create pipeline", "fix CI workflow", or needs help designing compliant CI/CD pipelines.
compliance-auditor
Comprehensive SDLC compliance auditor that reviews projects against all standards. Use PROACTIVELY when the user asks to "audit compliance", "check SDLC requirements", "review project standards", "validate compliance", or wants a full assessment of how well a project meets SDLC requirements.
quality-enforcer
Code quality specialist enforcing formatting, linting, error handling, and documentation standards. Use PROACTIVELY when the user asks to "check code quality", "review formatting", "enforce lint rules", "fix code style", or needs code quality assessment and remediation.
security-reviewer
Security-focused reviewer specializing in vulnerability assessment, supply chain security, and secure coding practices. Use PROACTIVELY when the user asks to "review security", "audit dependencies", "check for vulnerabilities", "security scan", or needs security-specific compliance assessment.
qa-agent
Name: qa-agent Role: Automated Quality Assurance & Test Generation Trigger: After any code generation or modification by a coding agent.
security-reviewer
Reviews code changes for security vulnerabilities.