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-verify/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-verify)<a href="https://agentmods.dev/skills/okuzpe/midas-harness/midas-verify"><img src="https://agentmods.dev/badge/skills/okuzpe/midas-harness/midas-verify/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-verify"><img src="https://agentmods.dev/badge/skills/okuzpe/midas-harness/midas-verify.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.01614 |
| Opus 5 | $0.00030 | $0.00807 |
| Sonnet 5 | $0.00012 | $0.00323 |
| Haiku 4.5 | $0.00006 | $0.00161 |
Grade A, and why
midas-verify 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.
How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
midas-verify — end-to-end / UI verification
Guard + state:
<paths.engine>/templates/skill-state-ritual.md(+AGENTS.md§ Safety / Path resolution). Precondition: landed sprint that touches UI (or--scope mobilefor native). Else report and stop. Tally shape:<paths.engine>/templates/audit-checklists.md§ Parseable tally lines.
Does / Does not
| Does | Does not |
|---|---|
| Prove acceptance criteria in a running app | Advance stage or set gate: passed |
Freeze evidence to {runs}/verifications/verify-NN.md |
Commit e2e/ suites to {product}/ |
Feed fail rows to /close-sprint as drift |
Run browser automation on API-only sprints |
Behavioral proof against sprint acceptance criteria — rung 4 of <paths.engine>/rules/verification.md. /close-sprint audits diff vs rules; this audits the living UI. Tool ladder, pre-checks, and fallback order: that rule §4 + <paths.engine>/templates/verify-record.md § Tool column — do not duplicate here.
HARD GATE — scope and cost
Browser/native automation is expensive. Do not pay blindly.
- Read
{product}/sprints/NN-*.mdacceptance criteria, sprint diff,{product}/architecture.md(clienttype). - Resolve
--scope:api— test runner /@playwright/clionly; no browser.web(default for web products) — agent-browser preferred; Playwright MCP fallback.mobile— Maestro MCP for native/hybrid only.all— web + mobile sections in one record.
- Non-UI sprint → skip browser MCPs; say so; freeze lighter record (same filename, no screenshots).
- Cheapest tool per claim; non-empty Tool column every row.
Procedure
1. Read state + criteria
Load paths.state, sprint file, {product}/design-system.md, {product}/design-direction.md, {product}/architecture.md, token files. Resolve sprint id, --scope, --profile. Determine run/preview command + URL.
2. Bring up the app
Start dev/preview in background; confirm serving. Ephemeral/test profile only — never production.
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 · 100 lines · 59 tokens per session scan A 9e2fcae38242
midas-verify is a skill published in the GitHub repository okuzpe/midas-harness (2 stars, last pushed 4d ago), licensed Apache-2.0. It adds 59 tokens to every session and 1,614 once invoked, about $0.0003 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
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…
pyats-dynamic-test
Generate and execute deterministic pyATS aetest validation scripts - interface state, OSPF neighbors, BGP paths, ping matrices, and custom compliance tests. Use when writing a network test, validating post-change state, running pass/fail checks, or building automated regression tests.
test-loop
Plan, generate, and heal an executable E2E test suite from approved acceptance criteria (web and mobile).
playwright-cli
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…