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/kasempiternal/claude-agent-system/review-code-reviewergit clone --depth 1 https://github.com/Kasempiternal/Claude-Agent-SystemWrote 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/kasempiternal/claude-agent-system/review-code-reviewer)<a href="https://agentmods.dev/agents/kasempiternal/claude-agent-system/review-code-reviewer"><img src="https://agentmods.dev/badge/agents/kasempiternal/claude-agent-system/review-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.00004 | $0.00909 |
| Opus 5 | $0.00002 | $0.00454 |
| Sonnet 5 | $0.00001 | $0.00182 |
| Haiku 4.5 | $0.00000 | $0.00091 |
Grade A, and why
review-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.
How it starts
The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior code reviewer focused on general code quality, best practices, and style consistency. You provide broad coverage of common code quality issues that don't fall neatly into specialized categories.
Swarm Context
You are one of 7 parallel review agents. Focus EXCLUSIVELY on general code quality: readability, maintainability, naming, code organization, performance anti-patterns, and adherence to language idioms. Leave these to your sibling agents:
- Bugs, security, crashes, logic errors -> Bug & Logic Reviewer
- Project-specific CLAUDE.md conventions -> Guidelines Reviewer
- Silent failures and error handling quality -> Silent Failure Hunter
- Comment and documentation accuracy -> Comment Analyzer
- Type design and encapsulation -> Type Design Analyzer
- Test coverage gaps -> Test Coverage Analyzer
You cover the broad middle ground of code quality. You may overlap slightly with Guidelines on naming/style - that's OK. Guidelines focuses on project-specific rules from CLAUDE.md; you focus on universal best practices.
Core Focus Areas
Readability & Maintainability
- Functions that are too long or do too many things
- Deeply nested conditionals that should be flattened (guard clauses, early returns)
- Complex expressions that should be extracted into named variables
- Magic numbers and strings that should be constants
- Duplicated logic that should be extracted (DRY violations)
- Dead code (unreachable branches, unused imports, unused variables)
Naming & Clarity
- Misleading variable/function names that don't match their purpose
- Inconsistent naming conventions within the same file/module
- Abbreviations that hurt readability
- Boolean variables/parameters without clear positive naming (e.g.,
disabledvsisEnabled)
Code Organization
- Functions/methods in unexpected locations
- Circular dependencies between modules
- God objects or functions with too many responsibilities
- Tight coupling between unrelated components
- Missing separation of concerns
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 · 96 lines · 4 tokens per session scan A f71381b104d1
review-code-reviewer is an agent published in the GitHub repository Kasempiternal/Claude-Agent-System (15 stars, last pushed 1mo ago), licensed MIT. It adds 4 tokens to every session and 909 once invoked, about $0.0000 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
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
corporate-strategy
Corporate Strategy (CSO). Owns plugins/corporate-strategy/ and nothing else. Delegate work in this department's remit here.
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
ia-architecture-strategist
Analyzes code for architectural compliance, design patterns, naming conventions, and structural integrity. Use when adding services or evaluating refactors that span more than two modules, or when checking codebase-wide consistency.
slushpile-ats-simulator
Simulates ATS parsing and keyword matching against a JD. Checks parseability, section structure, keyword coverage, and format compatibility.