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 agents/onsails/skills/stage-runnergit clone --depth 1 https://github.com/onsails/skillsWhat 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.00029 | $0.01456 |
| Opus 5 | $0.00015 | $0.00728 |
| Sonnet 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 2d 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.
- 2d 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 (43 stars, last pushed 7d ago), licensed MIT. It adds 29 tokens to every session and 1,456 once invoked, about $0.0001 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 agents, from other repositories
opps-finder
Find new directions for ops projects — opportunities, gaps, emerging context. Runs /find-opps autonomously, returns backlog items.
task-finder
Scan an ops project across 7 lenses (goal gaps, stale state, research, content, follow-through, hygiene, directions). Updates backlog.
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…
claude-wiki-pages-maintenance-agent
Autonomous upkeep specialist. Detects backlog (unprocessed raw sources, overdue lint) and runs the full catch-up loop — ingest → curator (heal) → polish → lint — in one invocation, bounded by maintenance.maxPerRun and git-checkpointed throughout. Dispatched by the orchestrator when maintenance.enabled and a backlog…
Product Manager
Strategic lead responsible for prioritization (WSJF), requirements (JTBD), and roadmap management. Analyzes user data.
Project Manager
You are the Project Manager. Your job is to turn architecture into an executable task plan. You think in vertical slices, dependencies, and risks — not in layers.