midas-harness: Skill for Claude Code

.agents/skills/close-sprint/SKILL.md

close-sprint is a skill for Claude Code, Codex from okuzpe/midas-harness. It costs 88 tokens per session (1,612 once invoked), scanned A, original, Apache-2.0.

A final check for a development sprint, comparing the completed code with the agreed rules and product scope.

In plain words
What is it for?
Use it after tasks and tests are complete to audit the sprint, resolve differences, save the result, and choose the next sprint or finish the MVP.
Why use it?
It catches work that drifted from the plan and records whether the sprint is ready to close or needs changes.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents); mentions AGENTS.md.

This is okuzpe/midas-harness's own configuration. It tells Claude Code and Codex how to work on midas-harness itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything midas-harness configures →

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/close-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.

agentmods badge for close-sprint

README.md
[![agentmods](https://agentmods.dev/badge/skills/okuzpe/midas-harness/close-sprint/github.svg)](https://agentmods.dev/skills/okuzpe/midas-harness/close-sprint)
Your own site
<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.

agentmods 80×15 button for close-sprint

Your own site · 80×15
<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>
Per session 88 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,612 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.

ModelPer sessionOnce 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

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

Security

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.

.agents/skills/close-sprint/SKILL.md · 73 lines

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-sprint ran the pre-sprint drift audit and set the sprint active. close-sprint is the formal Phase-8 gate — only after tasks, tests, and UI /midas-verify journeys (web and/or mobile sections in verify-NN.md, when applicable) are green. Never open a sprint with close-sprint; never ship a gate without it.

Precondition. A sprint must be active in paths.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 sweep product + 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-hygiene or internals /midas-sweep / /midas-lean-review.
  • Step 0.5 — Diff gate receipts (when production paths changed): require {paths.cache}/gates/<run>/test.json and quality.json with isPassingReceipt semantics (pass or skipped + reason) or record an explicit skip with reason in {runs}/sprints/NN-progress.md or audit notes. Engine-only / docs-only diffs: skip OK. When receipts are missing or stale, path-pass <paths.engine>/skills/midas-diff-gates/SKILL.md and run its receipt commands in this same close run — still not Skill-tool invoke. Does not change verify-NN.md semantics — UI/API proof stays /midas-verify (primary; human-typed when needed).
  • Step 1 — Read state + frozen rules: paths.state (honor track: lite{product}/market.md optional; {product}/business-plan.md still 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.md with MIDAS_AUDIT_RESULT tally; unresolved=0 required before closing.
  • Step 6 — Plan adjustment + update state: set sprint status: done; set the matching {product}/roadmap.md Status cell to done; reconcile sprints[]; 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.mjs after sprint done (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 run node <paths.scripts>/capture-candidates.mjs --progress {runs}/sprints/NN-progress.md — propose only; never auto-write rules/playbooks.

Read the full file on GitHub · 73 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.

  1. 4d ago Changed 9fd10ecf03c4
  2. 9d ago First seen · 73 lines · 88 tokens per session scan A 88b0ff9876fa

Subscribe to this mod's changes

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.

Related

Other skills, from other repositories

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

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens