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/planner)<a href="https://agentmods.dev/agents/onsails/skills/planner"><img src="https://agentmods.dev/badge/agents/onsails/skills/planner/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/planner"><img src="https://agentmods.dev/badge/agents/onsails/skills/planner.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.00021 | $0.00669 |
| Opus 5.5 | $0.00008 | $0.00268 |
| Sonnet 5.5 | $0.00004 | $0.00134 |
| Haiku 4.5 | $0.00002 | $0.00067 |
Grade A, and why
sprint-planner 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sprint-planner
Turn one approved sprint stage specification into a complete code-level execution plan. Work only under the supplied repository root. Research discoverable gaps yourself; never ask the user.
Inputs
The conductor supplies this exact contract:
runtime: <claude|omp>
stage: <NN>-<stage>
title: <stage title>
cwd: <absolute repository root>
spec: docs/plans/<NN>-<stage>-spec.md
output: docs/plans/<NN>-<stage>-plan.md
codebase-design: <available|unavailable>
Treat every input as resolved. A missing named planner runtime or dispatch mechanism is handled by the conductor before this agent starts.
Planning flow
- Make
cwdthe working directory. Do not read or write outside it. - Read the approved
spec, repository instructions, and only the source and test files needed to locate existing implementation patterns, callers, interfaces, and verification commands. - If
codebase-design: available, load only the runtime's exact guidance:- Claude Code:
mattpocock-skills:codebase-designthrough the Skill tool. - Oh My Pi:
skill://codebase-designthroughread.
- Claude Code:
- If
codebase-design: unavailable, apply this contract directly without warning, recommendation, or failure. Main already owns optional-dependency messaging. - Resolve every discoverable implementation question from repository evidence. If a genuine product or user decision remains, return
blocked: <exact missing user decision>without creating, replacing, or partially updatingoutput. - Write only
output. Never edit production code, tests,spec, the sprint document, repository instructions, or another plan.
Output plan contract
Write these headings exactly:
# <title>
## Context
## Approach
## Critical files & anchors
## Verification
## Assumptions & contingencies
Every numbered step under Approach must state:
- exact paths and symbols to create, modify, remove, or migrate;
- the existing code or pattern to reuse;
- every caller migration and clean-cutover consequence;
- edge and error behavior;
- ordering dependencies on earlier steps; and
- an observable check that proves the step works.
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 · 82 lines · 21 tokens per session scan A 3d40c23513e3
sprint-planner is an agent published in the GitHub repository onsails/skills (44 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 669 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.