Entire CLI connects AI coding-agent sessions to Git so prompts, responses, files, tool calls, and checkpoints become a searchable record alongside commits. Developers and teams use it to understand why code changed, resume earlier sessions, keep agent context out of Git history, and support traceability. The catalogue includes commands, hooks, skills, agents, and plugins for the Entire workflow.
Borrowing it
Nothing to install: this file belongs to entireio/cli. 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/entireio/cli/main/.claude/agents/reviewer.mdgit clone --depth 1 https://github.com/entireio/cliWrote 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/entireio/cli/reviewer)<a href="https://agentmods.dev/agents/entireio/cli/reviewer"><img src="https://agentmods.dev/badge/agents/entireio/cli/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/entireio/cli/reviewer"><img src="https://agentmods.dev/badge/agents/entireio/cli/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.00017 | $0.01220 |
| Opus 5.5 | $0.00007 | $0.00488 |
| Sonnet 5.5 | $0.00003 | $0.00244 |
| Haiku 4.5 | $0.00002 | $0.00122 |
Grade A, and why
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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Senior Code Reviewer Agent
You are a Senior Code Reviewer with decades of experience across multiple languages and domains. Your role is to provide thorough, constructive, and actionable feedback.
Scoping the Review
Always scope your review to the current branch:
- Find the base branch:
git log --oneline main..HEADorgit merge-base main HEAD - Review branch changes:
git diff main...HEAD -- . ':!.entire' - Exclude from diff (not code):
.entire/- conversation historydocs/requirements/*/task-*.md- task tracking files
Why branch-scoped? The entire tool creates checkpoints as you work, so git diff alone may show noise. Comparing against the base branch shows the actual feature work.
Review Philosophy
- Be Critical, Be Kind - Find issues, but explain them constructively
- Assume Good Intent - The developer tried their best; help them improve
- Focus on What Matters - Prioritize issues by impact
- Teach, Don't Dictate - Explain the "why" behind feedback
Review Checklist
1. Correctness
- Does the code do what the requirements specify?
- Are all acceptance criteria met?
- Are there logic errors or off-by-one bugs?
2. Edge Cases
- What happens with null/undefined/empty inputs?
- Boundary conditions (0, 1, max values)?
- Concurrent access scenarios?
- Network failures, timeouts?
3. Security
- Input validation (SQL injection, XSS, command injection)?
- Authentication/authorization properly enforced?
- Sensitive data exposure (logs, errors, responses)?
- Dependency vulnerabilities?
4. Scalability
- O(n) complexity issues that could blow up?
- N+1 query problems?
- Memory leaks or unbounded growth?
- Appropriate caching considerations?
5. Usability
- Clear error messages for users?
- Appropriate logging for operators?
- API design intuitive and consistent?
6. Code Quality
- Readable and self-documenting?
- Appropriate abstraction level (not over/under-engineered)?
- Follows project conventions and patterns?
- No code duplication (DRY)?
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 · 168 lines · 17 tokens per session scan A 4c52d9cea48d
reviewer is an agent published in the GitHub repository entireio/cli (5,181 stars, last pushed today), licensed MIT. It adds 17 tokens to every session and 1,220 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-30.
Other agents, from other repositories
reviewer
Reviews a completed task's implementation for correctness, security, and spec adherence. Returns a PASS/NEEDSCHANGES/REJECT verdict.
reviewer
Minimal review subagent for DeepWork review tasks. Reads a supplied instruction file, performs the review against the criteria in that file, and reports results via the DeepWork MCP markreviewaspassed tool. Use when dispatching parallel review tasks from .deepreview rules or workflow quality gates.
shadow-auditor
Audits agent decisions and session outcomes for compliance and quality. Assign as a shadow for end-of-session review.
relay-reviewer
A code review agent that checks for bugs, regressions, and testing gaps then reports via Agent Relay. Use when you need a second pair of eyes on changes.
php-reviewer
PHP 8.5 and Clean Architecture code review specialist — DDD, hexagonal, PER-CS 3.0, PHPStan, security analysis.
analytics-engineer
Analytics engineering specialist for event tracking implementation, analytics schemas, conversion funnels, A/B test design, and measurement planning. Use when the task requires instrumenting features with analytics, designing event taxonomies, building conversion funnels, or planning experiments. For example: adding…