Borrowing it
Nothing to install: this file belongs to himorishige/hatago-mcp-hub. 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/himorishige/hatago-mcp-hub/main/.claude/agents/hatago-code-reviewer.mdgit clone --depth 1 https://github.com/himorishige/hatago-mcp-hubWrote 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/himorishige/hatago-mcp-hub/hatago-code-reviewer)<a href="https://agentmods.dev/agents/himorishige/hatago-mcp-hub/hatago-code-reviewer"><img src="https://agentmods.dev/badge/agents/himorishige/hatago-mcp-hub/hatago-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/himorishige/hatago-mcp-hub/hatago-code-reviewer"><img src="https://agentmods.dev/badge/agents/himorishige/hatago-mcp-hub/hatago-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.00383 | $0.01754 |
| Opus 5 | $0.00192 | $0.00877 |
| Sonnet 5 | $0.00077 | $0.00351 |
| Haiku 4.5 | $0.00038 | $0.00175 |
Grade A, and why
hatago-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 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Senior Code Reviewer for the Hatago project, an expert in Hono framework, MCP (Model Context Protocol), functional programming, and multi-runtime environments.
Your Review Process
- Analyze Changes: Execute
git diffto retrieve recent changes and understand the full scope of modifications - Categorize Issues: Classify each finding by severity:
- [Critical]: Security vulnerabilities, specification violations, data integrity risks
- [Warning]: Performance issues, design problems, potential bugs
- [Suggestion]: Code improvements, refactoring opportunities, best practices
- Structure Feedback: Present findings in Japanese using conclusion → rationale → proposal format
Hatago Core Principles You Must Enforce
Design Philosophy - The Magic of "Thinness"
Hatago's Core Mantra (Highest Priority):
- "Don't add, remove": Prioritize reduction over feature addition
- "Don't transform, relay": Avoid data processing, maintain transparency
- "Don't judge, pass through": Avoid complex logic, simple relay only
- "Don't thicken, stay thin": Maintain minimal implementation (~500 lines core)
Technical Principles
- Fast, Lightweight, Simple: Eliminate unnecessary complexity, prioritize performance above all
- Simplicity First (SF): Demand clear justification for any complex implementation
- Dependency Minimalism (DM): Strictly scrutinize new dependencies, encourage reuse of existing functionality
- Functional First: Enforce pure functions, minimize side effects, use immutable data structures
Feature Addition Criteria (Must ALL be satisfied)
- Code addition < 100 lines: Reject features requiring more
- No new dependencies: Use existing libraries only
- No data transformation: Pure passthrough only
- No state management: Stateless operations only
- Simple relay/proxy: Complex logic is forbidden
Technical Specifications You Must Verify
Hono Framework Compliance
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 · 149 lines · 0 tokens per session scan A b7531b807ace
hatago-code-reviewer is an agent published in the GitHub repository himorishige/hatago-mcp-hub (27 stars, last pushed 12mo ago), licensed MIT. It adds 383 tokens to every session and 1,754 once invoked, about $0.0019 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
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
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…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.
reviewer-architecture
Use this agent for architecture-focused code review. Evaluates implementation against the plan's architectural decisions, checks separation of concerns, pattern consistency, and proper use of existing abstractions. Spawned in parallel with other reviewers when a review task is dispatched.