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.
git clone --depth 1 https://github.com/morimorijap/sunaba-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/morimorijap/sunaba-cli/reviewer)<a href="https://agentmods.dev/agents/morimorijap/sunaba-cli/reviewer"><img src="https://agentmods.dev/badge/agents/morimorijap/sunaba-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/morimorijap/sunaba-cli/reviewer"><img src="https://agentmods.dev/badge/agents/morimorijap/sunaba-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.00043 | $0.00147 |
| Opus 5.5 | $0.00017 | $0.00059 |
| Sonnet 5.5 | $0.00009 | $0.00029 |
| Haiku 4.5 | $0.00004 | $0.00015 |
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.
What it actually says
reviewer
Read git diff. Compare against the most recent
claudedocs/plans/<...>.md.
Report findings ordered by severity:
- 🛑 Blocker — likely regression, missing test, plan deviation the user did not authorize.
- ⚠ Concern — taste / maintainability / scope creep.
- ✅ Note — non-blocking observations.
Cite paths in path:line form. Do not rewrite the implementation.
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 · 19 lines · 43 tokens per session scan A 2facbe5ba193
reviewer is an agent published in the GitHub repository morimorijap/sunaba-cli (4 stars, last pushed 26d ago), licensed MIT. It adds 43 tokens to every session and 147 once invoked, about $0.0002 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
code-reviewer
Revisa código com foco em qualidade, consistência com o projeto e lições aprendidas. Use proativamente após escrever ou modificar código. Apenas leitura — nunca modifica arquivos.
agent-creator
Use this agent when the user asks to "create an agent", "generate an agent", "build a new agent", "make me an agent that...", or describes agent functionality they need. Trigger when user wants to create autonomous agents for plugins. Examples: Context: User wants to create a code review agent user: "Create an agent…
skill-reviewer
Use this agent when the user has created or modified a skill and needs quality review, asks to "review my skill", "check skill quality", "improve skill description", or wants to ensure skill follows best practices. Trigger proactively after skill creation. Examples: Context: User just created a new skill user: "I've…
type-design-analyzer
Use this agent when you need expert analysis of type design in your codebase. Specifically use it (1) when introducing a new type to ensure it follows best practices for encapsulation and invariant expression, (2) during pull request creation to review all types being added, and (3) when refactoring existing types to…
code-reviewer
Reviews code for bugs, logic errors, security vulnerabilities, code quality issues, and adherence to project conventions, using confidence-based filtering to report only high-priority issues that truly matter.
pr-test-analyzer
Use this agent when you need to review a pull request for test coverage quality and completeness. This agent should be invoked after a PR is created or updated to ensure tests adequately cover new functionality and edge cases. Typical triggers include the user asking whether tests on a freshly-created PR are thorough…