What is start-sprint?

A sprint-start skill that checks a planned set of development work against the project's rules and scope before coding begins.

Use it to start or resume a planned sprint and mark it as active after the required planning gate has passed.

It catches changes or inconsistencies that have appeared since planning and produces a working plan for the sprint.

How okuzpe/midas-harness configures Claude Code and Codex

Reuse

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.

Copy the file

curl -O https://raw.githubusercontent.com/okuzpe/midas-harness/main/.agents/skills/start-sprint/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/okuzpe/midas-harness

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/okuzpe/midas-harness/start-sprint/github.svg)](https://agentmods.dev/skills/okuzpe/midas-harness/start-sprint)

Your own site

<a href="https://agentmods.dev/skills/okuzpe/midas-harness/start-sprint"><img src="https://agentmods.dev/badge/skills/okuzpe/midas-harness/start-sprint/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/okuzpe/midas-harness/start-sprint"><img src="https://agentmods.dev/badge/skills/okuzpe/midas-harness/start-sprint.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 70 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,445 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00070	$0.02445
Opus 5	$0.00035	$0.01222
Sonnet 5	$0.00014	$0.00489
Haiku 4.5	$0.00007	$0.00245

Measured 4d ago against content hash 714efb262157, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

start-sprint 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 4d 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.

.agents/skills/start-sprint/SKILL.md · 139 lines

How it starts

The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.

start-sprint (Phase 7 — Sprint Execution kickoff)

Guard + state: <paths.engine>/templates/skill-state-ritual.md (+ AGENTS.md § Safety / Path resolution).

This is "applying the harness" — the signature loop. Before any code is written for a sprint, the orchestrator re-audits the living code against the rules frozen in Phase 5 and the scope in the business case, reconciles drift, picks the agents, and emits a working plan. Then implementation proceeds on the build tier with Context7.

vs /close-sprint: start-sprint = pre-sprint drift audit + working plan + set sprint active. close-sprint = formal Phase-8 gate after tasks are done, tests green, and UI journeys verified. Do not substitute one for the other — run start at kickoff, close at the gate.

Precondition. A sprint must be planned (or active being resumed) in paths.state → sprints[], and Phase 6's gate must be passed. If no sprint is selectable, stop and report.

Kickoff only. Full Phase-7 implementation (task loop, inner verify→fix, acceptance) lives in <paths.engine>/pipeline/7-sprint-execution.md — follow it after this skill sets the sprint active.

Does / Does not

Does	Does not
Pre-sprint audit of living code vs frozen rules + MVP scope	Render the Phase-8 conformance verdict (`/close-sprint`)
Queue fix-tasks or log conscious rule amendments	Silently ignore drift
Emit working plan; set sprint `active` after confirm; sync `{product}/roadmap.md` Status	Implement the sprint tasks here (that is build / Phase 7 body)
Cost-aware agent/tier selection + Context7 library list	Replace `/plan-sprints` (no plan yet → plan first)

When NOT

No sprint planned / Phase 6 not passed → /plan-sprints (or /midas-status).
Tasks already done and ready to grade → /close-sprint (after /midas-verify when UI).
Ad-hoc investigation outside the sprint → /midas-explore.
Only need orientation → /midas-status / /midas-recall.

Read the full file on GitHub · 139 lines

Changes

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.

4d ago Changed · +1 lines 714efb262157
9d ago First seen · 138 lines · 70 tokens per session scan A e2bfa8220985

Subscribe to this mod's changes

start-sprint is a skill published in the GitHub repository okuzpe/midas-harness (2 stars, last pushed 4d ago), licensed Apache-2.0. It adds 70 tokens to every session and 2,445 once invoked, about $0.0003 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-31.

Project management

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

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…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

story-readiness

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…

Donchitos/Claude-Code-Game-Studios · 77 tokens

autotask-creator

Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.

Orkas-AI/Orkas · 5 tokens

remove

Remove a deployed framework or addon from the current workspace.

jmagly/aiwg · 12 tokens

midas-harness: Skill for Claude Code