Borrowing it
Nothing to install: this file belongs to okuzpe/midas-harness. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/okuzpe/midas-harness/main/.agents/skills/plan-sprints/SKILL.mdgit clone --depth 1 https://github.com/okuzpe/midas-harnessWrote 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/okuzpe/midas-harness/plan-sprints)<a href="https://agentmods.dev/skills/okuzpe/midas-harness/plan-sprints"><img src="https://agentmods.dev/badge/skills/okuzpe/midas-harness/plan-sprints/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/okuzpe/midas-harness/plan-sprints"><img src="https://agentmods.dev/badge/skills/okuzpe/midas-harness/plan-sprints.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.00069 | $0.01659 |
| Opus 5.5 | $0.00028 | $0.00664 |
| Sonnet 5.5 | $0.00014 | $0.00332 |
| Haiku 4.5 | $0.00007 | $0.00166 |
Grade A, and why
plan-sprints 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
plan-sprints (Phase 6 — Sprint Planning)
Guard + state:
<paths.engine>/templates/skill-state-ritual.md(+AGENTS.md§ Safety / Path resolution). Playbook:<paths.engine>/pipeline/6-sprint-planning.md
Sequence the MVP only into shippable sprints. Value is correct decomposition and dependency ordering, not prose volume. Each sprint is a thin, demonstrable slice whose Definition of Done points at Phase-5 rules — that is what makes the Phase-8 audit possible.
Precondition. Read
paths.state. Run whenstage: architecture_rulesispassed(orsprint_planningresuming). If the rules/design system are not frozen, stop and report.
Does / Does not
| Does | Does not |
|---|---|
| Plan MVP-only roadmap + per-sprint files with EARS acceptance + rule-named DoD | Pull non-goals into scope or invent post-MVP work |
| Keep sprint 1 independently shippable; prefer many thin sprints | Fat “kitchen-sink” sprints that absorb “just one more” feature |
Seed {product}/features.json (status: failing) + sprints[] planned |
Self-advance stage or start implementation (/start-sprint does that) |
When NOT
- Rules/design system not frozen (
track: full) →/define-conventionsfirst. - When
track: lite, lean<paths.rules>/or engine-base rules count as frozen;{product}/design-system.mdis optional — do not redirect to/define-conventionssolely because design-system is missing. See<paths.engine>/pipeline/lite.md. - Sprints already planned and you only need to kick off →
/start-sprint. - Mid-sprint task tracking → path-pass
midas-progress(internal; replan only if the human explicitly asks).
Anti-rationalization: a sprint that keeps absorbing scope is a fail — split it. Do not merge extras into sprint 1 so it stops being independently shippable. Soft target: ≤ 5 concrete tasks per sprint file unless the human accepts a written exception in the sprint’s non-scope notes.
Inputs
paths.state,{product}/business-plan.md(MVP scope + non-goals + success metrics),{product}/architecture.md, effective rules (<paths.engine>/rules/*+<paths.rules>/*),{product}/design-system.md.- When
track: lite,{product}/market.mdis optional — do not hard-stop if it is missing.{product}/business-plan.mdis still required (Lite Idea+Plan writes a thin stub). See<paths.engine>/pipeline/lite.md.
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 Changed · +9 lines f95e1459d13d
- 2mo ago First seen · 98 lines · 69 tokens per session scan A 27fa33b47195
plan-sprints is a skill published in the GitHub repository okuzpe/midas-harness (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 69 tokens to every session and 1,659 once invoked, about $0.0003 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-31.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
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.
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…
remove
Remove a deployed framework or addon from the current workspace.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…