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/verifier)<a href="https://agentmods.dev/agents/morimorijap/sunaba-cli/verifier"><img src="https://agentmods.dev/badge/agents/morimorijap/sunaba-cli/verifier/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/verifier"><img src="https://agentmods.dev/badge/agents/morimorijap/sunaba-cli/verifier.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.00037 | $0.00179 |
| Opus 5.5 | $0.00015 | $0.00072 |
| Sonnet 5.5 | $0.00007 | $0.00036 |
| Haiku 4.5 | $0.00004 | $0.00018 |
Grade A, and why
verifier 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
verifier
Invoke .claude/hooks/verify.sh. Read its exit code and the
structured stderr.
- Exit 0. All checks passed. Compare against the plan's Acceptance Criteria. If criteria match, signal done. If not, request a clarification.
- Exit 2 (
SUNABA_VERIFY_FAILED). Read.sunaba/autopilot/last-failure.log. Surface the specific failing command. Do NOT propose a fix here — the orchestrator will dispatch the implementer. - Exit 1 (
SUNABA_BUDGET_EXCEEDED). Stop. Hand off to human review.
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 · 20 lines · 37 tokens per session scan A 56e942587355
verifier is an agent published in the GitHub repository morimorijap/sunaba-cli (4 stars, last pushed 26d ago), licensed MIT. It adds 37 tokens to every session and 179 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-31.
Other agents, from other repositories
agent-sdk-verifier-py
Use this agent to verify that a Python Agent SDK application is properly configured, follows SDK best practices and documentation recommendations, and is ready for deployment or testing. This agent should be invoked after a Python Agent SDK app has been created or modified.
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…
test-engineer
Writes characterization, contract, and equivalence tests that pin down legacy behavior so transformation can be proven correct. Use before any rewrite.
Smart Exclude
Picks folders a SAST run doesn't need to scan (test directories, fixtures, docs, generated code, vendored deps) so the scan skips them.
test-failure-analyst
Reads test output and source to explain why a test fails. Use after a failing test run.
tester
A test-writing agent that designs and implements unit, integration, and end-to-end tests. End-to-end tests check a complete user or system flow from start to finish.