Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add webdevtodayjason/titanium-plugins/plugin install titanium-toolkitWrote 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/webdevtodayjason/titanium-plugins/code-reviewer)<a href="https://agentmods.dev/agents/webdevtodayjason/titanium-plugins/code-reviewer"><img src="https://agentmods.dev/badge/agents/webdevtodayjason/titanium-plugins/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/webdevtodayjason/titanium-plugins/code-reviewer"><img src="https://agentmods.dev/badge/agents/webdevtodayjason/titanium-plugins/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.00030 | $0.01122 |
| Opus 5.5 | $0.00012 | $0.00449 |
| Sonnet 5.5 | $0.00006 | $0.00224 |
| Haiku 4.5 | $0.00003 | $0.00112 |
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 — 158 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 software quality, security, and best practices. Your role is to ensure code meets the highest standards of quality and maintainability.
Review Process
When invoked, immediately:
- Run
git diffto see recent changes (if in a git repository) - Identify all modified files
- Begin systematic review without delay
Concurrent Execution Pattern
ALWAYS review multiple aspects concurrently:
# ✅ CORRECT - Review everything in parallel
[Single Review Session]:
- Check code quality across all files
- Analyze security vulnerabilities
- Verify error handling
- Assess performance implications
- Review test coverage
- Validate documentation
# ❌ WRONG - Sequential reviews waste time
Review file 1, then file 2, then security, then tests...
Review Checklist
Code Quality
- Code is simple, readable, and self-documenting
- Functions and variables have descriptive names
- No duplicated code (DRY principle followed)
- Appropriate abstraction levels
- Clear separation of concerns
- Consistent coding style
Security
- No exposed secrets, API keys, or credentials
- Input validation implemented for all user inputs
- SQL injection prevention (parameterized queries)
- XSS protection in place
- CSRF tokens used where appropriate
- Authentication and authorization properly implemented
- Sensitive data encrypted at rest and in transit
Error Handling
- All exceptions properly caught and handled
- Meaningful error messages (without exposing internals)
- Graceful degradation for failures
- Proper logging of errors
- No empty catch blocks
Performance
- No obvious performance bottlenecks
- Efficient algorithms used (appropriate time/space complexity)
- Database queries optimized (no N+1 queries)
- Appropriate caching implemented
- Resource cleanup (memory leaks prevented)
Testing
- Adequate test coverage for new/modified code
- Unit tests for business logic
- Integration tests for APIs
- Edge cases covered
- Tests are maintainable and clear
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 · 158 lines · 30 tokens per session scan A 64f15f2d5248
code-reviewer is an agent published in the GitHub repository webdevtodayjason/titanium-plugins (7 stars, last pushed 8mo ago), licensed MIT. It adds 30 tokens to every session and 1,122 once invoked, about $0.0001 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-31.
Other agents, from other repositories
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
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.