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 BASHBOP/otito --skill otito-reviewgit clone --depth 1 https://github.com/BASHBOP/otitoWrote 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/bashbop/otito/otito-review)<a href="https://agentmods.dev/skills/bashbop/otito/otito-review"><img src="https://agentmods.dev/badge/skills/bashbop/otito/otito-review/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/bashbop/otito/otito-review"><img src="https://agentmods.dev/badge/skills/bashbop/otito/otito-review.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.00035 | $0.00225 |
| Opus 5.5 | $0.00014 | $0.00090 |
| Sonnet 5.5 | $0.00007 | $0.00045 |
| Haiku 4.5 | $0.00003 | $0.00022 |
Grade A, and why
otito-review 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
otito review (procedure)
Use this before merge or when the user asks if a change is safe to land.
Local changes
otito review . --request "<what changed>" --base origin/main --json
otito gate . --base origin/main
GitHub PR
otito review . --pr <number> --json
otito gate --pr <number> --path .
Interpretation
| Verdict | Action |
|---|---|
| PASS | No blocking signals; human still owns merge |
| WARN | Inspect flagged checks explicitly |
| FAIL | Do not merge until resolved |
MCP equivalents
- Review context only:
review_context - Gate only:
review_gate - Full composite:
review_verdict
Treat gate output as deterministic evidence — not model opinion.
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 · 39 lines · 35 tokens per session scan A 0c1f1093befc
otito-review is a skill published in the GitHub repository BASHBOP/otito (2 stars, last pushed 25d ago), licensed MIT. It adds 35 tokens to every session and 225 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 skills, from other repositories
github
Skill "github" from Hmbown/Codewhale, covering github, when to use, setup, workflow and non-goals.
git-iris
Use this skill when generating commit messages, pull request descriptions, release notes, changelogs, or code reviews in a repository where git-iris is available. Activates on requests like "commit this", "write a commit message", "draft a PR", "generate release notes", "write a changelog", or "review my changes" when…
shipping-and-launch
Prepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.
push-handoff
Commit and push a verified handoff plus its artifacts, only under explicit authority, and prove the push happened by reading the remote SHA back. Use as the final delivery step after artifacts are ready, when the user asks to push work, or when a handoff needs to reach the remote. Refuses to claim success without…
diffctx
Use when reviewing or explaining a commit, PR, branch or uncommitted diff — "review my last commit", "review before merge", "review my changes", "what else does this change affect" — the callers and tests the change reaches outside its diff, then the surrounding code.
land
Drive open PRs to merged — re-establish each PR's real state, resolve review threads, conflicts, failing checks, and CI failures under a bounded repair budget, land only the contiguous verified run bottom-up through the project's forge, watch until the checks pass and each merge lands, and stop at the ceiling. Use…