What is midas-status?

A read-only status command for the Midas workflow that reports the current phase, its gate status, and the next action.

It is for checking the Midas state file, identifying the current phase, and reporting the single next command or action.

It helps you understand where a workflow stopped or how to resume without changing files or advancing its state.

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/midas-status/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/midas-status/github.svg)](https://agentmods.dev/skills/okuzpe/midas-harness/midas-status)

Your own site

<a href="https://agentmods.dev/skills/okuzpe/midas-harness/midas-status"><img src="https://agentmods.dev/badge/skills/okuzpe/midas-harness/midas-status/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/midas-status"><img src="https://agentmods.dev/badge/skills/okuzpe/midas-harness/midas-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 2,258 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.00044	$0.02258
Opus 5	$0.00022	$0.01129
Sonnet 5	$0.00009	$0.00452
Haiku 4.5	$0.00004	$0.00226

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

Security

Grade A, and why

midas-status 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 9d 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/midas-status/SKILL.md · 118 lines

How it starts

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

midas-status — where am I, what's next

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

A cheap, read-only status check. It never writes, never advances state, and never runs a gate to completion — it reports the truth already on disk. Safe to run at any time, including mid-phase.

Lost on which skill? Do not invent a second router — use docs/skills.md § Which command when (install: <paths.engine>/docs/skills.md) or /midas-help. Audit roles: same file § Audits (+ <paths.engine>/templates/audit-checklists.md).

Steps

Read the state file at paths.state. If it is missing, report that Midas is not installed → run npx github:okuzpe/midas-harness --diagnose or /midas-reconcile (or install per INSTALL.md). If it exists but setup_complete is not true, the single next action is /midas-init (finish the one-time setup) regardless of stage — say so and stop. If it exists but does not parse, say so plainly and point at /midas-doctor.
Resolve the current stage from stage + stage_status against the 9-phase table in <paths.engine>/state.schema.md and <paths.engine>/methodology.md.
Re-derive gate status (read-only). For the current phase, check whether its required artifacts exist on disk and summarize which gate items are satisfied vs outstanding. Do not grade the gate as passed here — that is the orchestrator's job at phase transition. Just report observed state: not_started / in_progress / gate_pending / passed, with the missing items if any.
Print the single next action. Map the current stage to exactly one recommended command — for the user to type. The phase rituals are gated (disable-model-invocation); never call the Skill tool on them (it errors) — present the command (e.g. "👉 Run /define-conventions"), don't invoke it.

Runtime table: read <paths.engine>/stage-command-table.yaml on disk (parsed by <paths.scripts>/stage-command-table.mjs). That YAML is generated from STAGE_ROWS in stage-command-table.mjs — engine maintainers edit the JS rows, then doctor --fix / align. Do not duplicate the YAML in this skill — resolve each run from the file:

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

9d ago First seen · 118 lines · 44 tokens per session scan A 5d5032296a7d

Subscribe to this mod's changes

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

Planning

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

midas-harness: Skill for Claude Code