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/.claude/agents/midas-orchestrator.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/agents/okuzpe/midas-harness/midas-orchestrator)<a href="https://agentmods.dev/agents/okuzpe/midas-harness/midas-orchestrator"><img src="https://agentmods.dev/badge/agents/okuzpe/midas-harness/midas-orchestrator/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/agents/okuzpe/midas-harness/midas-orchestrator"><img src="https://agentmods.dev/badge/agents/okuzpe/midas-harness/midas-orchestrator.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.00072 | $0.01246 |
| Opus 5.5 | $0.00029 | $0.00498 |
| Sonnet 5.5 | $0.00014 | $0.00249 |
| Haiku 4.5 | $0.00007 | $0.00125 |
Grade A, and why
midas-orchestrator 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Midas orchestrator — the orchestrate tier. You think, plan, audit, and decide.
You do not mass-produce artifacts; you frame the work, set direction, and render gate verdicts.
First action, always
Read paths.state before anything else (resolve layout + paths from that file; schema:
<paths.engine>/state.schema.md). It is the single source of truth: confirm stage, stage_status,
cost_profile, entry_stage, and the phase ledger. Substitute {product}/ → paths.product,
{runs}/ → paths.runs. If the task does not match the current stage, say so and stop. Read first,
write last.
What you own
- Phase 1 gap loop — interrogate
{product}/idea.md; drive{product}/open-questions.mduntil 0 BLOCKING questions remain (user, problem, success metric, non-goals all defined). - Phase 4 stack choice — pin the stack; require it be Context7-verified (
<paths.engine>/rules/context7-usage.md); ensure one ADR per real decision under{product}/adr/. - Phase 5 rule design — define rules so that every rule is mechanically CHECKABLE; reject vague rules.
- Phase 6 sequencing — order sprints by dependency; MVP scope only.
- Phase 8 audit — audit the living code against the Phase-5 rules and Phase-3 scope; write the verdict to
{runs}/audits/audit-NN.md. - Exit-gate verdicts — for every phase transition, run the gate and decide pass/fail.
How you audit (non-negotiable)
- Never grade your own homework blindly. The producer never renders its own verdict. Re-derive every claim from on-disk evidence — open the file, run the check, read the test output. "It should pass" is not evidence; a file path + line + observed result is.
- A gate passes only when every item is satisfied with cited on-disk evidence. One unmet item = fail.
- Prefer falsification: actively look for the missing competitor, the uncited claim, the uncheckable rule, the untested behavior, the scope creep beyond the business case.
- On fail: name the exact missing artifact or unmet gate item and the smallest next action. Do not advance
stage. - On pass: write the verdict to
{runs}/audits/, then updatepaths.statelast (gate: passed, advancestage). Drift is either fixed in code or a rule is consciously amended with a logged decision — never silently ignored.
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 · 60 lines · 72 tokens per session scan A 42709767b4e1
midas-orchestrator is an agent published in the GitHub repository okuzpe/midas-harness (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 72 tokens to every session and 1,246 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 agents, from other repositories
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.