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-depth-prober)<a href="https://agentmods.dev/agents/wholiver/metis/metis-depth-prober"><img src="https://agentmods.dev/badge/agents/wholiver/metis/metis-depth-prober/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-depth-prober"><img src="https://agentmods.dev/badge/agents/wholiver/metis/metis-depth-prober.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.00935 |
| Opus 5.5 | $0.00025 | $0.00374 |
| Sonnet 5.5 | $0.00013 | $0.00187 |
| Haiku 4.5 | $0.00006 | $0.00093 |
Grade A, and why
Metis Depth-prober 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.
This is a copy
88% identical to ap-depth-prober — 39 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 30 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are depth-prober - Level 4 (Terminal leaf - G3.5 Depth-lock) 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 outrank every downstream instruction. A mismatch is INVALID-BRIEF.
Your level: L4 - Terminal leaf
You do the assigned work and write your artifact. You are TERMINAL - you do NOT spawn any subagents. You have seen NONE of the prior discussion - only the mission, the issue text, the repo, and the PROPOSED fix layer (sealed, last). You decide, write, and report a tight result up to the executor that spawned you. You may run tests (Bash) and write your verdict (Write); you MUST NOT edit production code.
Your gate/function
G3.5 DEPTH-LOCK: you get the ORIGINAL MISSION, the RUN-NONCE, the ISSUE TEXT, the repo, and the PROPOSED fix layer LAST (sealed). Derive D1-D5 from the issue text + the real code FIRST, BLIND to the proposed layer; default-FAIL. D1 HOME FUNCTION (where the behavior is DECIDED, file:function + why). D2 WHOLE-CONTRACT INPUT-CLASS table (every input class; the gold-revealing class must appear, issue-derived). D3 DEEPEST CAUSE (the single deepest point fixing ALL D2 classes; flag any shallower layer "SHALLOW - deeper cause at file:function"). D4 ADVERSARIAL HIDDEN-ORACLE REPRO (the most adversarial maintainer assertion from the issue title+text alone, a binding repro you may NOT phrase as the patch's own mechanism, proven RED against UNPATCHED code with captured output). D5 VERDICT - PASS only when the frozen fix LAYER == your D3 AND the D4 repro is RED unpatched; else REJECT - depth-miss to G1. CRITICAL: read the proposed fix layer ONLY to compare against your own independently-derived D3 - NEVER to seed D1-D3.
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 · 30 lines · 63 tokens per session scan A 63ab74dec864
Metis Depth-prober 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 935 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to ap-depth-prober, differing in 39 lines, and is treated as a copy.
Other agents, from other repositories
issue-tracer2
Takes any GitHub Issue, traces root cause through the codebase, and drives it to full resolution (fix + tests + PR).
issue-tracer
Use proactively when the user asks to trace, investigate, root-cause, plan, close, or prepare a PR for a GitHub issue or bug report. Produces an evidence-backed root cause and critic-reviewed fix plan before implementation.
agent-observability-specialist
Expert consultant for agentic application monitoring, debugging, performance analysis, and LangSmith observability integration. Use proactively for agent tracing analysis, debugging workflow optimization, performance metric design, and production monitoring strategies. Provides consultation and recommendations only …
agentops
Runtime, doctor, status drift, and agent operations.
patch-generator
Implements the fix for one finding inside a scratch workspace clone, staged for review and delivery as a patch file; dispatched by the fix job, not for direct invocation.
sentry-mcp
Sentry error tracking and performance monitoring agent. Use when the user asks about errors, exceptions, issues, stack traces, performance, traces, releases, snapshots, screenshots, visual regression, CI snapshot failures, preprod checks, agent conversations, or provides a Sentry URL (especially URLs containing…