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 skills add morimorijap/sunaba-cli --skill verify-changegit 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/skills/morimorijap/sunaba-cli/verify-change)<a href="https://agentmods.dev/skills/morimorijap/sunaba-cli/verify-change"><img src="https://agentmods.dev/badge/skills/morimorijap/sunaba-cli/verify-change/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/skills/morimorijap/sunaba-cli/verify-change"><img src="https://agentmods.dev/badge/skills/morimorijap/sunaba-cli/verify-change.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.00000 | $0.00095 |
| Opus 5.5 | $0.00000 | $0.00038 |
| Sonnet 5.5 | $0.00000 | $0.00019 |
| Haiku 4.5 | $0.00000 | $0.00010 |
Grade A, and why
verify-change 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
verify-change
Use after implementation, before final response.
Steps
- Inspect
git diff --statandgit diff. - Run the smallest relevant checks (typecheck, lint, the touched test file).
- Report failures with exact command output, not paraphrased.
- Record unresolved risk in
claudedocs/traces/<short-name>.mdonly when it is genuinely useful for future sessions.
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 · 13 lines · 0 tokens per session scan A 839d1bccf922
verify-change is a skill published in the GitHub repository morimorijap/sunaba-cli (4 stars, last pushed 26d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 95 tokens. 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 skills, from other repositories
expert-code-refactoring
Expert code refactoring for Java, JavaScript, and React projects. Focuses on SOLID principles, design patterns, and idiomatic improvements while ensuring test stability.
code-reviewer
Expert code reviewer specializing in code quality, security, performance, and maintainability across multiple programming languages. Use this skill when the user wants a PR review, code analysis, or suggestions for improvement. This skill includes proprietary checklists and a mandatory review template located in its…
pr-review
Checklist para abrir ou revisar pull request. Valida qualidade do código, spec, testes e segurança antes de abrir ou aprovar qualquer PR.
.claude
Review changes for correctness, tests, and generated-output drift. When Claude specific behavior is relevant, call out the generated .claude surface.
.gemini
Review changes for correctness and test evidence. Keep recommendations concise and reference the generated .gemini surface only when needed.
code-review
Review changes for correctness, tests, and generated-output drift. Treat .agents, .claude, .cursor, and .gemini as projected runtime surfaces.