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 agentmods add skills/bashbop/otito/otito-reviewnpx 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.svg" alt="Measured on agentmods" 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 | $0.00035 | $0.00225 |
| Opus 5 | $0.00017 | $0.00112 |
| Sonnet 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 4d 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.
- 4d ago First seen · 39 lines · 35 tokens per session scan A 0c1f1093befc
otito-review is a skill published in the GitHub repository BASHBOP/otito (1 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 225 once invoked, about $0.0002 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-31.
Other skills, from other repositories
publish
Publish the Octop Python package: cut a release branch from develop, bump version, update CHANGELOG, open a PR to main; after merge, Actions tag on main (PyPI / Docker Hub + GHCR) and sync main into develop. Use when the user asks to publish, release, bump version, cut a release, or run /publish.
forge-release
Merge approved issue code to production branch and trigger deployment. Use this skill when an issue has been approved at staging and needs to be released — squash-merges the ISS- feature branch to the production branch, triggers Coolify deploy, and closes the issue. Triggers on: /forge-release, releasing an issue…
devops-pipeline
Build, test-package, and release the Prime-Silo desktop app (Space Agent). Use when asked to build the app, make a local/test build, package for Windows/macOS/Linux, cut a release, bump the version, or debug the release CI. Covers the Open-Studio companion services (opencode + open-notebook) bundling.
release-notes-drafter
Use when drafting customer-facing release notes from merged PRs and changelog fragments.
prime-silo-devops
DevOps, SDLC, Tagging, and Release management instructions for Prime-Silo. Use this when asked to tag a new release, check CI/CD build status, or manage the SDLC.
release-notes
Generate a CHANGELOG.md entry from git history since the last tag, categorized by type (features, fixes, security, breaking changes). Matches the existing CHANGELOG format.