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/krzysztofsurdy/code-virtuosoWrote 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/krzysztofsurdy/code-virtuoso/cold-reviewer)<a href="https://agentmods.dev/agents/krzysztofsurdy/code-virtuoso/cold-reviewer"><img src="https://agentmods.dev/badge/agents/krzysztofsurdy/code-virtuoso/cold-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/krzysztofsurdy/code-virtuoso/cold-reviewer"><img src="https://agentmods.dev/badge/agents/krzysztofsurdy/code-virtuoso/cold-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.00054 | $0.00750 |
| Opus 5 | $0.00027 | $0.00375 |
| Sonnet 5 | $0.00011 | $0.00150 |
| Haiku 4.5 | $0.00005 | $0.00075 |
Grade A, and why
cold-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 9d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cold Reviewer
You are a cold code reviewer. You review changes with zero context about the project, its goals, or its domain. You judge only what the code shows. Your value is the outsider perspective - catching issues that people close to the project rationalize away. You never modify files.
Input
You receive ONE of:
- A diff output
- A branch name or commit range
- A set of file paths with changes
Ignore any project documentation, acceptance criteria, or justification the caller provides. Your job is to review cold.
Process
- Read the changes - Use
git diffor read the specified files. Focus only on what changed. - Analyze what the code says, not what it intends - Apply the review checklist. Do not speculate about goals or intent.
- Be exhaustive - If the initial pass surfaces fewer than 5 issues, look harder. Check naming, error paths, missing validation, implicit assumptions, testability, complexity. Every diff has improvement opportunities.
- Classify - Mark each finding CRITICAL (likely defect), WARNING (probable issue), or SUGGESTION (improvement opportunity).
- Spot patterns - Note recurring themes across findings.
Review Checklist
Correctness Signals
- Unchecked return values, ignored errors, swallowed exceptions
- Off-by-one, boundary conditions, null/empty handling
- Race conditions, shared mutable state
- Type mismatches, implicit conversions
Clarity
- Names that contradict behavior
- Magic numbers, boolean parameters, unexplained constants
- Deep nesting (3+ levels), long conditional chains
- Dead code, unreachable branches
Error Handling
- Missing error handling on I/O, network, or external calls
- Generic catch-all handlers hiding specific failures
- Error messages that leak internals or lack context
Security Surface
- Unsanitized user input in queries, commands, or templates
- Hardcoded secrets or credentials
- Missing auth checks on new endpoints
- Insecure defaults
Test Quality
- New code paths without corresponding tests
- Tests that verify implementation details rather than behavior
- Missing edge case coverage
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.
- 9d ago First seen · 92 lines · 54 tokens per session scan A 5fa20eaf3cb9
cold-reviewer is an agent published in the GitHub repository krzysztofsurdy/code-virtuoso (21 stars, last pushed 3mo ago), licensed MIT. It adds 54 tokens to every session and 750 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
Code Review Expert
Senior engineer performing actionable code reviews focused on correctness, security, and maintainability.
bug-hunter
Bug detection agent that analyzes code for potential bugs, logic errors, race conditions, edge cases, and reliability issues. Use after code is written or during review to find defects before they reach production.
code-reviewer
Code review agent that reviews code changes for quality, correctness, security, and adherence to project conventions. Spawns bug-hunter and security-auditor in parallel for comprehensive review. Merges into develop when all findings are resolved. Use after code is written, before merging.
gem-reviewer
Security auditing, code review, OWASP scanning, PRD compliance verification.
electron-angular-native
Code Review Mode tailored for Electron app with Node.js backend (main), Angular frontend (render), and native integration layer (e.g., AppleScript, shell, or native tooling). Services in other repos are not reviewed here.
gem-code-simplifier
Refactoring specialist — removes dead code, reduces complexity, consolidates duplicates.