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/close-sprint/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/close-sprint)<a href="https://agentmods.dev/skills/okuzpe/midas-harness/close-sprint"><img src="https://agentmods.dev/badge/skills/okuzpe/midas-harness/close-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.
<a href="https://agentmods.dev/skills/okuzpe/midas-harness/close-sprint"><img src="https://agentmods.dev/badge/skills/okuzpe/midas-harness/close-sprint.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.00088 | $0.01612 |
| Opus 5 | $0.00044 | $0.00806 |
| Sonnet 5 | $0.00018 | $0.00322 |
| Haiku 4.5 | $0.00009 | $0.00161 |
Grade A, and why
close-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.
How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
close-sprint (Phase 8 — Per-sprint Audit & Adjust)
Guard + state:
<paths.engine>/templates/skill-state-ritual.md(+AGENTS.md§ Safety / Path resolution).
The closing half of the 7 ⇄ 8 loop. After a sprint's code lands, the orchestrator audits the living code against the rules frozen in Phase 5 and the scope in the business case, resolves drift, freezes the verdict, and decides what's next. The producer never grades its own homework — this is an independent orchestrate-tier audit.
vs
/start-sprint:start-sprintran the pre-sprint drift audit and set the sprintactive.close-sprintis the formal Phase-8 gate — only after tasks, tests, and UI/midas-verifyjourneys (web and/or mobile sections inverify-NN.md, when applicable) are green. Never open a sprint with close-sprint; never ship a gate without it.
Precondition. A sprint must be
activeinpaths.state → sprints[]with its work landed (tasks done, tests run). If no active sprint, stop and report.
Shared audit fragments:
<paths.engine>/templates/audit-checklists.md(gate semantics, evidence rule, tally format, hygiene hook). Record shape:<paths.engine>/templates/audit-record.md.
Procedure
Full procedure: <paths.engine>/pipeline/8-audit-adjust.md.
Step outline (Steps 0–6):
- Step 0 — Hygiene pass (path-pass, not Skill-tool): Read and follow
<paths.engine>/skills/midas-hygiene/SKILL.md(product scope — path-passes sweepproduct+ lean on fat diffs) when brownfield requires a sweep record or the diff is large (greenfield: recommended; document any skip). Do not Skill-tool / auto-slash; power-users may still type/midas-hygieneor internals/midas-sweep//midas-lean-review. - Step 0.5 — Diff gate receipts (when production paths changed): require
{paths.cache}/gates/<run>/test.jsonandquality.jsonwithisPassingReceiptsemantics (passorskipped+ reason) or record an explicit skip with reason in{runs}/sprints/NN-progress.mdor audit notes. Engine-only / docs-only diffs: skip OK. When receipts are missing or stale, path-pass<paths.engine>/skills/midas-diff-gates/SKILL.mdand run its receipt commands in this same close run — still not Skill-tool invoke. Does not changeverify-NN.mdsemantics — UI/API proof stays/midas-verify(primary; human-typed when needed). - Step 1 — Read state + frozen rules:
paths.state(honortrack: lite—{product}/market.mdoptional;{product}/business-plan.mdstill required), active sprint, all effective rules, architecture + idea docs, design system. - Step 2 — Conformance audit: every rule, pass/fail with on-disk evidence; confirm Context7 doc coverage; trigger every matching playbook. Risk-selected lenses: follow
<paths.engine>/pipeline/8-audit-adjust.md§ Risk-selected lenses (law:<paths.engine>/rules/verification.md). - Step 3 — Scope audit: delivered scope vs plan and business-case success metrics; no scope creep, no silent drops.
- Step 4 — Resolve drift: fix now or consciously amend the rule (+ ADR); re-render adapters if amended; nothing left silent.
- Step 5 — Freeze the audit: write
{runs}/audits/audit-NN.mdwithMIDAS_AUDIT_RESULTtally;unresolved=0required before closing. - Step 6 — Plan adjustment + update state: set sprint
status: done; set the matching{product}/roadmap.mdStatus cell todone; reconcilesprints[]; select next sprint or declare MVP complete. - Optional — lifecycle journal:
node <paths.scripts>/lifecycle-journal.mjs close_sprint --detail "sprint-NN"(fail-open metrics under{paths.cache}/metrics/lifecycle.jsonl). - Optional — quality log:
node <paths.scripts>/quality-log.mjs audit pass --detail "sprint-NN"(metadata-only JSONL; never secrets). - Optional — carryover refresh:
node <paths.scripts>/carryover-refresh.mjsafter sprintdone(snapshot → idle). Resume ladder:<paths.engine>/templates/session-resume-precedence.md. - Optional — capture proposals: after
{runs}/sprints/NN-progress.md§ Learned is filled, the human may runnode <paths.scripts>/capture-candidates.mjs --progress {runs}/sprints/NN-progress.md— propose only; never auto-write rules/playbooks.
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 9fd10ecf03c4
- 9d ago First seen · 73 lines · 88 tokens per session scan A 88b0ff9876fa
close-sprint is a skill published in the GitHub repository okuzpe/midas-harness (2 stars, last pushed 4d ago), licensed Apache-2.0. It adds 88 tokens to every session and 1,612 once invoked, about $0.0004 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.
Other skills, from other repositories
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.
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…
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.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.