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/stage-runner)<a href="https://agentmods.dev/agents/onsails/skills/stage-runner"><img src="https://agentmods.dev/badge/agents/onsails/skills/stage-runner/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/stage-runner"><img src="https://agentmods.dev/badge/agents/onsails/skills/stage-runner.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.00029 | $0.01456 |
| Opus 5.5 | $0.00012 | $0.00582 |
| Sonnet 5.5 | $0.00006 | $0.00291 |
| Haiku 4.5 | $0.00003 | $0.00146 |
Grade A, and why
sprint-stage-runner 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sprint-stage-runner
Run one sprint stage through isolate, execute, review, verify, commit, and land. Keep the conductor's context clean. Run repository commands from the repository root and follow skills/sprint/mechanics.md for the exact worktree and git commands. The sprint's manually created stage worktree is authoritative; do not use task isolation.
This agent is used only for Nesting: yes. The runtime must support the hierarchy it recorded. OMP requires task.maxRecursionDepth >= 3 for both main → sprint-stage-runner → sprint-reviewer → workers and main → sprint-stage-runner → sprint-stage-executor → SDD workers. If the required nested dispatch mechanism is unavailable, return blocked; never flatten the work into this agent or ask the user.
Inputs
The conductor passes every value below in the prompt. Treat each as resolved data, not a choice:
runtime—claudeoromp.engine—codex,mimo,native, orbare.sprint,stage,title, and plan path.- absolute
repoand absolute stageworktreepaths. review-effort—high,xhigh, ormax.review-model— (Claude only) the exact effective model selected for this stage's review.review-backend— the exact review reference resolved by the conductor. Pass it to the reviewer verbatim; never resolve, replace, or reinterpret it.model— (Claude only,engine: native) the exact selected executor model. Pass it to the executor asexecutor-model; this renames the field, never the model value.sdd—availableorunavailablefor mimo and native execution.- engine-specific inputs: codex effort, or mimo model, variant, and bare handle.
On Claude the conductor has already applied the native executor floor when resolving review-model; never select, translate, shorten, compare, downgrade, or replace either model. On OMP no model inputs are passed: each child's model is bound by its own agent definition (sprint-stage-executor → @task, sprint-reviewer → @slow); do not add, infer, or pass one.
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 · 69 lines · 29 tokens per session scan A b4afb3566fa1
sprint-stage-runner is an agent published in the GitHub repository onsails/skills (44 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 1,456 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
catchup-runner
Does the catch-up fan-out, impact analysis, and brief assembly for /catchup on Sonnet (cheaper/faster than the caller's session). Spawned by the /catchup and /ketchup skills with a pre-resolved time window. Not user-invoked directly.
plan-creation-eng-lead
Engineering and Delivery Lead for implementation planning. Produces work breakdown structures, effort estimates, dependency graphs, milestones, parallel opportunities, and risk registers. Use when you need structured delivery planning for any implementation topic.
task-executor
Use this agent to execute a single tracked task with TDD, commit, and PR creation in an isolated git worktree. Dispatched by /coco:loop for parallel execution. Context: Multiple tasks are ready with non-overlapping file ownership. /coco:loop dispatches parallel agents. assistant: "I'll dispatch task-executor agents…
sprint-review
Use this agent when the user closes a sprint, finishes a batch of commits, runs bd close, says 'sprint done', 'we're done', 'wrapping up', 'closing the sprint', 'what did we accomplish', or signals that a unit of work is complete. Also trigger proactively when a bd close command has just run or the user is asking what…
portfolio-surveyor
Read-only portfolio surveyor for the Agentic Engineer. Runs the cheap live-state survey across exactly the repositories the consuming deployment's Portfolio map names and returns ONE compact, fixed-shape digest of operate and advance signals — breakage, per-PR hygiene, review-lane state, triage, and roadmap state …
release-manager
Owns the release pipeline: certification checklists, store submissions, platform requirements, version numbering, and release-day coordination. Use for release planning, platform certification, store page preparation, or version management.