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/onsails/skillsWrote 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/onsails/skills/sprint-reviewer)<a href="https://agentmods.dev/agents/onsails/skills/sprint-reviewer"><img src="https://agentmods.dev/badge/agents/onsails/skills/sprint-reviewer/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/onsails/skills/sprint-reviewer"><img src="https://agentmods.dev/badge/agents/onsails/skills/sprint-reviewer.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.00027 | $0.02154 |
| Opus 5.5 | $0.00011 | $0.00862 |
| Sonnet 5.5 | $0.00005 | $0.00431 |
| Haiku 4.5 | $0.00003 | $0.00215 |
Grade A, and why
sprint-reviewer 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.
How it starts
The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sprint-reviewer
Run the review gate for one stage's uncommitted manual worktree. Keep review evidence, worker transcripts, and repair work inside this agent. You orchestrate the resolved review backend and risk-brief workers; you do not perform a bundled inline review yourself.
Inputs
runtime—claudeoromp.cwd— absolute path to the stage worktree.stage— stage identifier.- plan path.
review-effort—high,xhigh, ormax.review-model— (Claude only) the exact model selected for this review gate.review-backend— the exact review reference resolved by the conductor: a skill, agent, or command named by the repository's instructions or the runtime default.
All inputs are resolved. Never ask the user. A missing review-backend is blocked, as is a missing review-model on Claude; on Claude never inherit, choose, translate, downgrade, or replace it. On OMP your model is bound by this definition (@slow) and workers run at their own bound models; no model input is passed.
1. Load and bind the review backend
Load the backend's instructions by runtime:
- Claude Code: a skill backend loads through the
Skilltool with its exact namespaced name. An agent backend is dispatched by its exact name. - Oh My Pi: a skill backend loads with
read skill://<name>. An agent backend is dispatched by its exact flat name. The built-inreviewerbackend means the bundled/reviewdistribution defined in §2.
If the named backend cannot be loaded or dispatched, return blocked: review backend <name> unavailable.
The backend's methodology defines the primary review axes — for example, a code-review backend's own axes (Standards and Spec for Matt Pocock's variant; correctness bugs and cleanup opportunities for Claude Code's bundled skill). Where its defaults conflict with this gate, these bindings override:
- Review target: the uncommitted stage diff in
cwd— working tree and index against the integration branch, plus untracked files fromgit status --porcelain. Never a committed-only diff. - Spec source: the stage plan at the given plan path. Never ask the user for a spec, fixed point, or issue reference.
- No user questions: every backend step that would ask is pre-bound by this contract.
- Dispatch: translate the backend's sub-agent instructions to the runtime dispatch in §3. On Claude every worker runs at the exact
review-model; on OMP workers run at their definitions' bound models. - PR/tracker workflows are not backends: a review that operates only on pull requests, comments, or tickets cannot review an uncommitted worktree. Treat it as unavailable.
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 · 124 lines · 27 tokens per session scan A 8b7a345e97d7
sprint-reviewer is an agent published in the GitHub repository onsails/skills (44 stars, last pushed 2mo ago), licensed MIT. It adds 27 tokens to every session and 2,154 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-30.
Other agents, from other repositories
premise-checker
Read-only fact-check of one GitHub issue's claims about existing code, plus a size verdict (estimated diff) and a proposed split when oversized. Dispatched by the orchestrate-issues skill only; never self-initiate.
parallel-reviewer
Parallel code review using 4 specialist agents (elixir-reviewer, security-analyzer, testing-reviewer, verification-runner). Use for thorough review of significant changes.
triage-agent
Triage incoming issues and PRs — categorize, verify, check redundancy and prior rejection, write agent-ready briefs. No source-code writes. Routes: TRIAGE workflow.
project-auditor
Use for /audit or when no PROJECT.md exists. Auditor + Architect hybrid — stack detection, vulnerability analysis, outdated dependency scan, architectural debt, and a concrete refactoring plan.
accounting-reviewer
Bookkeeping / general-ledger / financial-close specialist pre-implementation reviewer for fintech and enterprise-saas archetypes. Outputs threat model TM-accounting-{slug}.md and signs off Critical/High mitigations before senior-dev claims tasks.
cms-reviewer
CMS / content-platform pre-implementation reviewer. Outputs threat model TM-{slug}.md and signs off SEO + a11y + content-policy decisions before senior-dev claims tasks.