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 skills add escapeboy/ai-prompts --skill sprint-orchestrategit clone --depth 1 https://github.com/escapeboy/ai-promptsWrote 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/skills/escapeboy/ai-prompts/sprint-orchestrate)<a href="https://agentmods.dev/skills/escapeboy/ai-prompts/sprint-orchestrate"><img src="https://agentmods.dev/badge/skills/escapeboy/ai-prompts/sprint-orchestrate/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/skills/escapeboy/ai-prompts/sprint-orchestrate"><img src="https://agentmods.dev/badge/skills/escapeboy/ai-prompts/sprint-orchestrate.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.00028 | $0.01671 |
| Opus 5.5 | $0.00011 | $0.00668 |
| Sonnet 5.5 | $0.00006 | $0.00334 |
| Haiku 4.5 | $0.00003 | $0.00167 |
Grade A, and why
sprint-orchestrate 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 8d 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sprint-orchestrate - Sprint Lifecycle Orchestrator
Chain skills into a complete development lifecycle where each phase feeds the next.
When to Use (and When NOT to)
| Use this skill for | Use a simpler approach for |
|---|---|
| A feature that needs the full Think→Plan→Build→Review→Test→Ship→Reflect chain | A single well-understood step (e.g. just testing) — run that one phase directly: /sprint-orchestrate [phase] [feature] |
| Coordinating multiple phases where each output feeds the next | A change that's already implemented and tested — run the Ship phase alone: /sprint-orchestrate ship [feature] |
| A sprint that needs metrics/insights captured afterward | A quick fix with no lasting design decisions to record — skip straight to /qa + the Ship phase, no need for Think/Plan/Reflect |
Usage
/sprint-orchestrate [phase] [feature-name]
Phases
| Phase | Skills Used | Output |
|---|---|---|
think |
Manual / brainstorm | Design doc at docs/design-[feature].md |
plan |
Architecture + test plan | docs/architecture-[feature].md, docs/test-plan-[feature].md |
build |
Implementation | Code on feature branch |
review |
Code review | Review findings |
test |
/qa |
Test results, regression tests |
ship |
Independent verifier gate → /commit + PR |
Merged PR |
reflect |
/retro |
Metrics, insights, action items |
full |
All phases sequentially | Complete sprint |
Behavioral Flow
Full Pipeline (/sprint-orchestrate full [feature])
-
Think: Ask the user six forcing questions:
- Who needs this? What are they doing today?
- What's the narrowest MVP someone would pay for?
- What would make someone say "whoa"?
- How does this compound over time?
Save answers to
docs/design-[feature].md.
-
Plan: From the design doc, create:
- Architecture plan with data flow and component design
- Test plan with edge cases and acceptance criteria
Save to
docs/architecture-[feature].mdanddocs/test-plan-[feature].md. - Probe the target host when the code will run somewhere other than this machine: a 60s SSH check of the binaries, data schema, auth state and SSH alias the plan assumes. Record every mismatch in the architecture doc before Build — they are cheap here and expensive at deploy.
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.
- 8d ago First seen · 140 lines · 28 tokens per session scan A d88a2ccd9160
sprint-orchestrate is a skill published in the GitHub repository escapeboy/ai-prompts (91 stars, last pushed 9d ago), licensed MIT. It adds 28 tokens to every session and 1,671 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-10-08.
Other skills, from other repositories
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…