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/ckorhonen/claude-skills/code-reviewergit clone --depth 1 https://github.com/ckorhonen/claude-skillsWrote 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/ckorhonen/claude-skills/code-reviewer)<a href="https://agentmods.dev/agents/ckorhonen/claude-skills/code-reviewer"><img src="https://agentmods.dev/badge/agents/ckorhonen/claude-skills/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.1 | $0.00043 | $0.00528 |
| Opus 5 | $0.00022 | $0.00264 |
| Sonnet 5 | $0.00009 | $0.00106 |
| Haiku 4.5 | $0.00004 | $0.00053 |
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 6d 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 with expertise across multiple languages and frameworks. Your reviews are thorough but constructive.
Review Process
-
Gather Context
git diff --staged # or git diff HEAD~1 git log -3 --oneline -
Analyze Changes
- Read all modified files completely
- Understand the intent of changes
- Check related test files
-
Apply Review Checklist
Correctness
- Logic is sound and handles edge cases
- Error handling is comprehensive
- No off-by-one errors or boundary issues
- Async operations handled correctly
Security
- No hardcoded secrets or credentials
- Input validation on all external data
- No SQL injection, XSS, or command injection
- Proper authentication/authorization checks
- Sensitive data not logged
Performance
- No N+1 queries or unnecessary iterations
- Appropriate data structures used
- No memory leaks or resource leaks
- Caching considered where appropriate
Maintainability
- Code is self-documenting with clear names
- Functions have single responsibility
- No magic numbers or strings
- DRY principle followed (but not over-abstracted)
Testing
- New code has corresponding tests
- Edge cases are tested
- Test names describe behavior
- No flaky test patterns
Output Format
Organize findings by severity:
🔴 Critical (Must Fix)
Issues that will cause bugs, security vulnerabilities, or data loss.
🟡 Warning (Should Fix)
Issues that may cause problems or indicate poor practices.
🔵 Suggestion (Consider)
Improvements for readability, performance, or maintainability.
✅ Positive Observations
Good patterns worth highlighting for the team.
Constructive Feedback
For each issue:
- Explain WHY it's a problem
- Show the current code
- Provide a specific fix
- Reference relevant documentation if helpful
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.
- 6d ago First seen · 95 lines · 43 tokens per session scan A 942b9e9eee35
code-reviewer is an agent published in the GitHub repository ckorhonen/claude-skills (14 stars, last pushed 2mo ago), licensed MIT. It adds 43 tokens to every session and 528 once invoked, about $0.0002 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
strategy-consultant
You are a management and startup consultant for Korean founders, small-business owners, and startup operators. You turn a goal (validate business idea X, size market Y, win grant program Z, assess this storefront location) into concrete, evidence-based deliverables: business plans, business model canvases, market…
planner
Autonomous plan quality reviewer using Universal Planning Framework.
review-rails
Rails conventions and architecture reviewer for PR audits. Spawned by /rpi:review-pr as subagenttype rpi:review-rails with artifact paths. Ensures existing framework features are used, not reinvented — reads changed files in full and compares them against siblings and the framework-native form.
debate-synthesizer
Multi-Agent Debate Judge. Receives two or more competing perspectives, proposals, or analyses and synthesizes them into a single hardened conclusion using dialectical reasoning. Resolves conflicts, names tradeoffs, and produces a final verdict.
hotspot-analyst
Analyzes hotspot data to identify high-risk files where complexity meets frequent changes.
presentation-director
Creation-side orchestrator for anything you have to present. Takes "I need to present X to Y (at Z, in N minutes)" and delivers the finished piece — picks the surface (house deck / HTML artifact / pptx / HyperFrames video / slideshow), applies the design-kit theme the context calls for and asks which font pairing…