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/midas-retro/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/midas-retro)<a href="https://agentmods.dev/skills/okuzpe/midas-harness/midas-retro"><img src="https://agentmods.dev/badge/skills/okuzpe/midas-harness/midas-retro/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/midas-retro"><img src="https://agentmods.dev/badge/skills/okuzpe/midas-harness/midas-retro.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.00064 | $0.01118 |
| Opus 5.5 | $0.00026 | $0.00447 |
| Sonnet 5.5 | $0.00013 | $0.00224 |
| Haiku 4.5 | $0.00006 | $0.00112 |
Grade A, and why
midas-retro 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 2mo 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
midas-retro — sprint retrospective (non-advancing)
Guard + state:
<paths.engine>/templates/skill-state-ritual.md(+AGENTS.md§ Safety / Path resolution). No stage precondition — runs anytime. Never mutatespaths.statestage/gates. Template:<paths.engine>/templates/retro-record.md→{runs}/retros/retro-NN.md.
Standing retrospective note (not a phase gate): capture what went well, what hurt, and durable
takeaways after a sprint. Distinct from /close-sprint (rule conformance + scope audit) and
/midas-progress (during-sprint STM rows).
Does / Does not
| Does | Does not |
|---|---|
Freeze {runs}/retros/retro-NN.md with learnings table |
Advance stage or pass Phase-8 gates |
| Read sprint file, progress STM, latest audit/verify | Rewrite architecture, rules, or features.json |
Emit MIDAS_RETRO_RESULT tally |
Replace /close-sprint, /midas-tribunal, or /midas-capture |
Args
| Arg | Meaning |
|---|---|
NN |
Sprint id (e.g. 01, 02) |
latest (default) |
Most recently done sprint, else active, else highest planned with a file |
--dry-run |
Print the draft in chat only — do not write the freeze file |
Procedure
1. Read state + pick sprint (scout)
Read paths.state. Resolve {runs}/ and {product}/. Choose sprint id from args / sprints[].
Require {product}/sprints/NN-*.md on disk. If missing → stop and name the path.
Dispatch scout for an index pack (paths + short excerpts, not whole trees):
- Sprint file: Goal, Acceptance, Tasks status, Blockers
{runs}/sprints/NN-progress.md§ Done / Learned (if present)- Latest
{runs}/audits/audit-NN.md/{runs}/verifications/verify-NN.mdwhen they exist - Open rows in
{product}/open-questions.mdtouched this sprint (if any)
2. Draft the retro (build)
Fill sections from the template:
| Section | Content |
|---|---|
| Went well | 3–7 concrete wins with evidence (path or test id) |
| Hurt | Friction, false starts, missing proof — no blame |
| Learned | Durable takeaways (candidates for /midas-capture if recurring) |
| Carry forward | Unfinished work / next-sprint inputs (not new scope invention) |
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.
- 2mo ago First seen · 93 lines · 64 tokens per session scan A 862a62371671
midas-retro is a skill published in the GitHub repository okuzpe/midas-harness (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 64 tokens to every session and 1,118 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,"…