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-reconcile/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-reconcile)<a href="https://agentmods.dev/skills/okuzpe/midas-harness/midas-reconcile"><img src="https://agentmods.dev/badge/skills/okuzpe/midas-harness/midas-reconcile/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-reconcile"><img src="https://agentmods.dev/badge/skills/okuzpe/midas-harness/midas-reconcile.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.00073 | $0.01089 |
| Opus 5 | $0.00036 | $0.00544 |
| Sonnet 5 | $0.00015 | $0.00218 |
| Haiku 4.5 | $0.00007 | $0.00109 |
Grade A, and why
midas-reconcile 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 5d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
midas-reconcile — which command should I run next?
Paths / state:
<paths.engine>/templates/skill-state-ritual.md(read-only) +AGENTS.md§ Path resolution.
Read-only. Never installs, never updates, never advances
stage. Prints the one next step from the diagnose CLI — do not re-implement detection in the model.
Use when:
npx ... updatefailed with "no existing Midas install"- You are not sure whether to run
/midas-initor/midas-adopt - You might be in a subfolder instead of the project root
Procedure
1. Run diagnose (source of truth)
If <paths.scripts>/install-diagnose.mjs exists as a file:
node <paths.scripts>/install-diagnose.mjs
# or machine-readable:
npx github:okuzpe/midas-harness --diagnose --json
Canonical v2 install: node .harness/scripts/install-diagnose.mjs
If that file is missing (engine sandbox seed, or paths.scripts points at repo scripts/):
# engine repo:
node cli/install-diagnose.mjs <product-root>
# otherwise:
npx github:okuzpe/midas-harness --diagnose
Do not assume paths.scripts existing as a directory means install-diagnose.mjs is there.
Run from the project root (or pass the path as the first argument).
2. Present the output verbatim
Statuses: not_installed | unsupported_v1 | setup_pending | version_behind | nested_or_wrong_cwd | partial_migrate | installer_incomplete | ready
Do not invent a different command unless the script is missing (fallback below).
3. Fallback (script missing — manual read)
| Observation | Next step |
|---|---|
No .harness/engine/VERSION, harness/VERSION, or .midas/engine/VERSION |
npx github:okuzpe/midas-harness#v{VERSION} --tools=cursor then /midas-init |
.harness/product or state.yaml without .harness/engine/VERSION |
/midas-init (partial_migrate) — do not treat as a fresh install |
Engine present and .harness/cache/installer/active.json exists |
npx … update --resume (or --rollback) — installer_incomplete |
harness/VERSION or .midas/engine/VERSION exists but canonical engine does not |
Pin [email protected], migrate to .harness/, then upgrade to 3.x. 3.x refuses 1.x trees. |
Engine present, setup_complete: false |
/midas-init |
v2 midas_version ≠ engine VERSION |
Same: npx …#v{VERSION} update --yes (or /midas-init for the tip) |
| Parent dir has Midas, this folder does not | cd to parent; /midas-status |
| Otherwise | /midas-status |
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.
- 5d ago Changed · +1 lines 1cb523213f4a
- 10d ago First seen · 87 lines · 73 tokens per session scan A c12ce25b8964
midas-reconcile is a skill published in the GitHub repository okuzpe/midas-harness (2 stars, last pushed 6d ago), licensed Apache-2.0. It adds 73 tokens to every session and 1,089 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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.