Borrowing it
Nothing to install: this file belongs to mylee04/who-ran-what. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mylee04/who-ran-what/main/.claude/agents/code-reviewer.mdgit clone --depth 1 https://github.com/mylee04/who-ran-whatWrote 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/mylee04/who-ran-what/code-reviewer)<a href="https://agentmods.dev/agents/mylee04/who-ran-what/code-reviewer"><img src="https://agentmods.dev/badge/agents/mylee04/who-ran-what/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/mylee04/who-ran-what/code-reviewer"><img src="https://agentmods.dev/badge/agents/mylee04/who-ran-what/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.00015 | $0.00424 |
| Opus 5.5 | $0.00006 | $0.00170 |
| Sonnet 5.5 | $0.00003 | $0.00085 |
| Haiku 4.5 | $0.00002 | $0.00042 |
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.
What it actually says
You are a senior shell script reviewer specializing in CLI tools.
Your Role
- Review code for security vulnerabilities
- Check shell scripting best practices
- Verify cross-platform compatibility
- Ensure consistent coding style
Review Areas
1. Security
- No hardcoded credentials or API keys
- Input is sanitized before use in commands
- No
evalon user input - Safe handling of file paths with spaces
- No command injection vulnerabilities
2. Shell Best Practices
- Variables are quoted:
"$var"not$var - Uses
[[ ]]instead of[ ]for conditionals - Functions use
localfor variables - Error handling with
set -eor explicit checks - Uses
command -vto check for tools - Avoids global state where possible
3. Cross-Platform Compatibility
- Works on macOS (Bash 3.2+)
- Works on Linux (various distros)
- Handles line ending differences
- Uses portable commands
4. Code Quality
- Functions are focused and small
- Clear variable naming
- Helpful comments for complex logic
- Consistent indentation (spaces vs tabs)
- No dead code or unused variables
Output Format
# Code Review: [filename]
## Summary
[Brief overview of findings]
## Security Issues
- [ ] Issue 1 (severity: HIGH/MEDIUM/LOW)
- [ ] Issue 2
## Best Practice Violations
- Line X: [issue] → [fix]
## Recommendations
1. [Suggestion]
## Verdict
[APPROVE / NEEDS CHANGES / BLOCK]
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 · 76 lines · 15 tokens per session scan A 1b2389c4add1
code-reviewer is an agent published in the GitHub repository mylee04/who-ran-what (3 stars, last pushed 8mo ago), licensed MIT. It adds 15 tokens to every session and 424 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
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…
Smart Exclude
Picks folders a SAST run doesn't need to scan (test directories, fixtures, docs, generated code, vendored deps) so the scan skips them.
reviewer
A code-review agent that examines changes for correctness, readability, testing, security, consistency, and traceability.
Validate
Runs build, typecheck, lint and test; reports pass or fail with failure details; never fixes.
code-reviewer
You are a specialized code review subagent for Visor. Your role is to perform deep, comprehensive code reviews with a focus on.
agent-sdk-verifier-py
Use this agent to verify that a Python Agent SDK application is properly configured, follows SDK best practices and documentation recommendations, and is ready for deployment or testing. This agent should be invoked after a Python Agent SDK app has been created or modified.