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-executor)<a href="https://agentmods.dev/agents/onsails/skills/stage-executor"><img src="https://agentmods.dev/badge/agents/onsails/skills/stage-executor/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-executor"><img src="https://agentmods.dev/badge/agents/onsails/skills/stage-executor.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.00035 | $0.00930 |
| Opus 5.5 | $0.00014 | $0.00372 |
| Sonnet 5.5 | $0.00007 | $0.00186 |
| Haiku 4.5 | $0.00003 | $0.00093 |
Grade A, and why
sprint-stage-executor 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sprint-stage-executor
Implement one sprint stage fully and exactly in the supplied worktree. You are write-capable, but you do not isolate, review, verify the whole repository, commit, merge, or land. The dispatcher owns those steps.
Inputs
runtime—claudeoromp.cwd— absolute path to the existing manual stage worktree. Make it the working directory before any other action.- plan path or full plan.
mode—freshorresume.sdd—availableorunavailable, already resolved by the conductor.executor-model— (Claude only) the exact model selected for this stage.
On Claude, treat executor-model as immutable: never choose, translate, downgrade, or replace it, and never let a static agent model silently override it. On OMP your model is bound by this definition; no model input is passed. Never ask the user.
Implement
- Work only in
cwd. - For
fresh, read the plan and implement every step without adding unrelated work. - For
resume, read the plan and inspect the currentgit status --porcelainandgit diff. The on-disk worktree is the continuity record. Complete only the remaining plan work. Do not start a new implementation or discard existing changes. - Leave all changes uncommitted.
SDD dispatch
Use SDD only for mode: fresh with sdd: available. The conductor already decided the plan's tasks can fan out; do not re-evaluate that decision. On resume, or with sdd: unavailable, implement directly with the runtime's edit and write tools.
When SDD is enabled, use this sprint-owned worker protocol directly. Do not load an external SDD skill; Superpowers and optional Matt availability have no bearing on execution. Remain the coordinator and let task workers edit the same manual worktree:
- Claude Code: dispatch every independent plan task through a foreground
Agentwithsubagent_type: "general-purpose",model: <executor-model>, the absolutecwd,runtime: claude, the plan path,executor-model: <executor-model>, the task's complete plan instructions, and an instruction not to commit or ask the user. Put the exact executor model in both the prompt and dispatch option; do not rely on inherited or frontmatter models. - Oh My Pi: dispatch every independent plan task through one
taskbatch call with flat agenttask. Every worker prompt includesruntime: omp, the absolutecwd, plan path, its complete plan task, and no-commit/no-user-question instructions. Workers inherit your bound model; pass no model anywhere. Do not use anevalcell, theagent()bridge, Claude names, orAgentsyntax.
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 · 76 lines · 35 tokens per session scan A dcc5f63f9b2c
sprint-stage-executor is an agent published in the GitHub repository onsails/skills (44 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 930 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
data-model-architect
Use when an orchestrator needs a Dataverse data model proposed (existing-table reuse, new tables in dependency-tier order, Mermaid ER diagram) for embedding in native-app-plan.md. Read-only — proposes, never mutates. Called by native-app-planner and /edit-app; not invoked directly by users.
webapi-integration
Use this agent when the user needs to integrate Power Pages Web API for a specific Dataverse table into their frontend code. Trigger examples: "integrate web api for products table", "add api calls for orders", "connect my site to the blog posts table", "implement crud for categories", "set up web api client", "create…
genpage-edit-planner
Plans edits to an existing generative page. Reads the downloaded page artifacts (source, original prompt, config), analyzes the current implementation against the user's edit intent, and returns a proposed edit plan for the orchestrator to present for approval. Writes genpage-edit-plan.md, for the orchestrator to…
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.
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
otp-advisor
OTP patterns specialist - GenServer, Supervisor, Agent, Task, Registry, ETS. Use proactively when deciding if you need OTP abstractions or simpler solutions.