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 brsbl/ottonomous --skill reviewgit clone --depth 1 https://github.com/brsbl/ottonomousWrote 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/brsbl/ottonomous/review)<a href="https://agentmods.dev/skills/brsbl/ottonomous/review"><img src="https://agentmods.dev/badge/skills/brsbl/ottonomous/review.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00083 | $0.01369 |
| Opus 5 | $0.00042 | $0.00685 |
| Sonnet 5 | $0.00017 | $0.00274 |
| Haiku 4.5 | $0.00008 | $0.00137 |
Grade A, and why
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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Input: $ARGUMENTS
Review the caller's target or implement fixes from caller-supplied findings. Return results inline unless the caller provides an output destination.
Resolve the invocation
Identify:
- Working location: repository or worktree to inspect
- Target: explicit diff command, refs/range, pull request, file set, staged changes, or branch changes
- Mode: review or fix
- Output destination: optional caller-selected location
- Fix selection: all findings, P0 only, or P0-P1
An explicit caller target always wins. When invoked without a target in a Git
repository, review the current branch against its merge base with the default
branch. staged means git diff --cached. State the exact scope and command
used so the review is reproducible.
Do not invent a review registry, fixed plan path, or hidden persistence. In fix mode, use findings supplied inline, by exact reference, or from the current conversation. If none are available, ask the caller for them.
Review mode
1. Inspect and categorize the change
Read the complete diff, list changed and untracked files in scope, and inspect the full source context needed to understand each change.
Assign architectural changes to the architect-reviewer persona in
$SKILL_DIR/agents/architect-reviewer.md:
- APIs, schemas, migrations, services, dependency boundaries, configuration, directory structure, and public contracts
Assign implementation changes to the senior-code-reviewer persona in
$SKILL_DIR/agents/senior-code-reviewer.md:
- UI, business logic, bug fixes, refactors, tests, and utilities
Assign a file to both when both lenses materially apply.
2. Delegate independent review
Scale to the change rather than a fixed ceremony:
- Small, cohesive diff: one reviewer with the appropriate persona
- Several independent components: one reviewer per meaningful component
- Large cross-cutting diff: multiple reviewers with explicit, non-overlapping scopes
Run independent scopes in parallel when the runtime supports it. Give every reviewer:
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 168 lines · 83 tokens per session scan A 2622ac36e0f9
review is a skill published in the GitHub repository brsbl/ottonomous (15 stars, last pushed 13d ago), licensed MIT. It adds 83 tokens to every session and 1,369 once invoked, about $0.0004 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-30.
Other skills, from other repositories
han-update-documentation
Update Han plugin documentation so every skill, agent, guidance doc, index, and cross-reference is current and accurate. On a non-default branch, scopes the pass to entities the branch actually touched. On the default branch, performs a full documentation sweep across the whole plugin. Use when updating, refreshing…
spike-consumer-baseline
OI-3 spike harness — heavy consumer skill, BASELINE arm. Builds an incident post-mortem and sources the readability standard mid-workflow by reading a file directly, with NO Skill-tool call. Use only when explicitly invoked by the spike harness with a TRIALID and data path.
spike-guidance-forked
OI-3 spike harness — the FORKED (context fork) readability-guidance variant. Same payload as the inline variant but declared to run in a forked context. Use only when a spike consumer skill invokes it.
spike-guidance-inline
OI-3 spike harness — the INLINE (non-forked) readability-guidance variant. Surfaces the shared readability standard into the calling skill's own context. Use only when a spike consumer skill invokes it.
spike-consumer-adversarial
OI-3 spike harness — heavy consumer, ADVERSARIAL arm. Worst-case early-exit test: the mid-workflow Skill call has no continuation guardrail and the guidance skill ends with a final-sounding anchor. Use only when explicitly invoked by the spike harness with a TRIALID and data path.
spike-guidance-adversarial
OI-3 spike harness — ADVERSARIAL inline guidance variant. Worst-case anchor: ends with a final-sounding completion statement and gives NO instruction to return to the caller. Use only when a spike consumer skill invokes it.