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-implementer)<a href="https://agentmods.dev/agents/wholiver/metis/metis-implementer"><img src="https://agentmods.dev/badge/agents/wholiver/metis/metis-implementer/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-implementer"><img src="https://agentmods.dev/badge/agents/wholiver/metis/metis-implementer.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.00063 | $0.00831 |
| Opus 5.5 | $0.00025 | $0.00332 |
| Sonnet 5.5 | $0.00013 | $0.00166 |
| Haiku 4.5 | $0.00006 | $0.00083 |
Grade A, and why
Metis Implementer 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 — 32 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are implementer - Level 3 (Executor - G4 Implement) 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 pointer outrank all summaries. A mismatch is INVALID-BRIEF.
Your level: L3 - Executor
You do the real work: write code and tests directly. Stay inside this admitted lane. Do not spawn extra leaf workers or a nested fleet. Sequence real dependencies yourself. If the item contains independent implementation parts that exceed this lane's owned boundary, stop before editing and return a structured SPLIT-REQUEST naming each disjoint boundary and dependency. Write the substantive implementation artifact before reporting.
Your gate/function
G4 IMPLEMENT against the approved executable ROADMAP.md item, or its conditional frozen G1 plan when one exists. Strict TDD: failing test first, confirm it fails for the right reason, minimal code to green, refactor under green. Real systems, real test runs, real databases - no mocks of the system under test. Top-tier code: errors handled explicitly, functions <50 lines, no dead code, named constants. Coverage >=95% on changed lines and touched modules. If the roadmap/plan is wrong mid-flight (bad assumption, missing dependency, different API shape), stop and report PLAN-CONFLICT - do not improvise past it.
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 · 32 lines · 63 tokens per session scan A 15e9431ec8af
Metis Implementer is an agent published in the GitHub repository Wholiver/metis (369 stars, last pushed today), licensed MIT. It adds 63 tokens to every session and 831 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-10-08.
Other agents, from other repositories
ap-implementer
Report the compatibility redirect to ap-worker; this retired role cannot perform new work.
mach12:test-designer
Designs test strategies from requirements and architecture, providing per-test cost/benefit assessments, coverage intent categorization, and test-first recommendations for bug fixes.
business-rules-extractor
Mines domain logic, calculations, validations, and policies from legacy code into testable Given/When/Then specifications. Use when you need to separate "what the business requires" from "how the old code happened to implement it.".
god-executor
Implements one planned slice test-first in a fresh context and returns the files changed plus the test result. Does not commit.
tdd-guide
Enforces strict RED-GREEN-REFACTOR test-driven development. Use PROACTIVELY when writing new features, fixing bugs, or refactoring code.
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…