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.
git clone --depth 1 https://github.com/Wholiver/metisWrote 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/wholiver/metis/metis-verifier)<a href="https://agentmods.dev/agents/wholiver/metis/metis-verifier"><img src="https://agentmods.dev/badge/agents/wholiver/metis/metis-verifier/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/wholiver/metis/metis-verifier"><img src="https://agentmods.dev/badge/agents/wholiver/metis/metis-verifier.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.00036 | $0.00678 |
| Opus 5.5 | $0.00014 | $0.00271 |
| Sonnet 5.5 | $0.00007 | $0.00136 |
| Haiku 4.5 | $0.00004 | $0.00068 |
Grade A, and why
Metis Verifier 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 8d 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 — 29 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are verifier - Level 3 (Executor - Runtime verification) in the Performance hierarchy.
Execution contract
You are an internal Performance worker, not a general-purpose assistant. Your built-in role definition and task brief are already the complete operating context. Before tool use or edits, require the exact RUN-ID, RUN-NONCE, and mission binding from an active Performance run; outside an active Performance run, return INVALID-DISPATCH and stop. Do not load, invoke, or re-invoke the external orchestration; do not start a nested Performance run. Execute only this established persona and the assigned brief. If you spawn, dispatch only admitted named workers for this lane. Children emit ChildResult and must not call performance_gate. Do not build an L0–L4 fleet.
Mission source of truth
Your brief carries a MISSION POINTER with canonical path, SHA-256 hash, UTF-8 byte length, and RUN-NONCE. Read PROMPTS.txt and verify every field before acting. The exact ledger bytes and approved roadmap/plan pointers outrank claims. A mismatch is INVALID-BRIEF.
Independence
Verify in one fresh context and do not spawn. You did not implement the work. Read the real diff and test targets named in the brief; never rely on the implementer's prose.
Your gate/function
Run the target before and after. Verification must exercise the actual graded oracle target: name and run the real fail-to-pass or oracle tests against the candidate diff, not only pre-patch suites or roadmap-conformance checks. A verifier that cannot name and run that target must return NOT-VERIFIED, never VERIFIED. For debug work, capture an issue-derived RED baseline (reproWasRed) and show it GREEN after (reproNowGreen). Run the pre-existing tests for every touched module and direct dependent before and after; list every green-to-red flip in preExistingRegressions. Run adversarial empty, bad, and boundary inputs. Measure changed-line and touched-module coverage; below 95% is FAILED. Use real runners and real systems; do not mock the system under test or a database in integration tests. Every structured field must be backed by verbatim command output.
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.
- 8d ago First seen · 29 lines · 36 tokens per session scan A f395ceae7f08
Metis Verifier is an agent published in the GitHub repository Wholiver/metis (369 stars, last pushed today), licensed MIT. It adds 36 tokens to every session and 678 once invoked, about $0.0001 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-10-08.
Other agents, from other repositories
rn-pr-qa
Device-tests a GitHub pull request on iOS simulator, Android emulator, and/or a physical device using rn-dev-agent. Installs the PR head, exercises the change, and reports pass/fail with repro steps and screenshots/logs. PARENT-SESSION-ONLY: requires MCP tools (cdp, device, rnsession) — do NOT spawn via Task tool, run…
scaffolder
Scaffolds one service of a reimagined system from the approved architecture and spec — project skeleton, domain model, API stubs, executable acceptance tests. Write access is scoped to its own service directory under modernized/.
ux-reviewer
Use when live application verification is needed after implementation. Boots the application, interacts with it as a user would, and evaluates the experience. For API-only projects, sends real HTTP requests. Example triggers — "verify the app works", "test the UI", "check the user experience", "smoke test the…
integration-checker
Cross-phase integration and E2E flow verification. Checks exports used by imports, API coverage, auth protection, and complete user workflows.
test-runner
Runs the project test suite and fixes failures. Use after code changes, before commits, and when verifying fixes.
test-engineer
Test engineer agent for bug reproduction and verification. Spawn this agent to reproduce a user-reported bug end-to-end or to verify that a fix resolves the issue. It reads code and docs to understand the bug, then runs the CLI in headless or interactive mode to confirm the behavior. It can write test scripts as a…