Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add okuzpe/midas-harness --skill midas-progressgit 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-progress)<a href="https://agentmods.dev/skills/okuzpe/midas-harness/midas-progress"><img src="https://agentmods.dev/badge/skills/okuzpe/midas-harness/midas-progress/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-progress"><img src="https://agentmods.dev/badge/skills/okuzpe/midas-harness/midas-progress.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.00059 | $0.00944 |
| Opus 5.5 | $0.00024 | $0.00378 |
| Sonnet 5.5 | $0.00012 | $0.00189 |
| Haiku 4.5 | $0.00006 | $0.00094 |
Grade A, and why
midas-progress 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
midas-progress — Sprint STM (session memory)
Guard + state:
<paths.engine>/templates/skill-state-ritual.md(+AGENTS.md§ Safety / Path resolution). Surface:internal(ADR-013) — prefer parent path-pass from/start-sprint/ Phase 7; power-user may still type this slash.
Paths:
{runs}/sprints/NN-progress.mdfrom template<paths.engine>/templates/sprint-progress.md. See<paths.engine>/rules/session-continuity.mdand<paths.engine>/research/memory-model.md.
Cheap write path for Phase 7 continuity. Updates the active sprint's progress file so /midas-recall and
Phase-8 audits see git-visible evidence of what was proved and how.
vs
/midas-recall: recall reads a context pack; progress writes STM. Status may suggest recall; progress is for after substantive work lands.
Preconditions
- Read
paths.state.stagemust besprint_executionwith anactivesprint insprints[]. - If
{runs}/sprints/NN-progress.mdis missing, copy from<paths.engine>/templates/sprint-progress.mdand fill the sprint id/title header.
Procedure
- Identify the delta from args or the current session:
- Completed task → append a Done row (
Task | Proof | Tool | Route). Include Route (inline/delegated/plan-first) when the task cluster spans ≥4 files (<paths.engine>/rules/organic-routing.md). - Significant decision → append an Observations subsection (What / Why / Where / Learned); note plan-first user acceptance in Learned when applicable.
- Update Next to the single following task or blocker.
- Refresh Last updated (ISO date).
- Completed task → append a Done row (
- Tool column — use canonical values from the template (
test-runner,context7,playwright-mcp, …). - Do not advance
stage, close the sprint, or edit{product}/features.jsonstatus here — that is implementation +/close-sprintterritory. - Print one line:
STM updated → {runs}/sprints/NN-progress.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.
- 2mo ago First seen · 74 lines · 59 tokens per session scan A 6700c4b13c41
midas-progress is a skill published in the GitHub repository okuzpe/midas-harness (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 59 tokens to every session and 944 once invoked, about $0.0002 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,"…