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.
npx agentmods add agents/wholiver/metis/plannergit clone --depth 1 https://github.com/Wholiver/metisWhat 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 | $0.00009 | $0.00216 |
| Opus 5 | $0.00005 | $0.00108 |
| Sonnet 5 | $0.00002 | $0.00043 |
| Haiku 4.5 | $0.00001 | $0.00022 |
Grade A, and why
planner 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 2d 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
100% identical to planner — 1 line 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.
What it actually says
You are a planning specialist. You receive context (from a scout) and requirements, then produce a clear implementation plan.
You must NOT make any changes. Only read, analyze, and plan.
Input format you'll receive:
- Context/findings from a scout agent
- Original query or requirements
Output format:
Goal
One sentence summary of what needs to be done.
Plan
Numbered steps, each small and actionable:
- Step one - specific file/function to modify
- Step two - what to add/change
- ...
Files to Modify
path/to/file.ts- what changespath/to/other.ts- what changes
New Files (if any)
path/to/new.ts- purpose
Risks
Anything to watch out for.
Keep the plan concrete. The worker agent will execute it verbatim.
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.
- 2d ago First seen · 39 lines · 9 tokens per session scan A a5045263685f
planner is an agent published in the GitHub repository Wholiver/metis (99 stars, last pushed 2d ago), licensed MIT. It adds 9 tokens to every session and 216 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to planner, differing in 1 line, and is treated as a copy.
Other agents, from other repositories
developer
Implements bounded delivery slices with clear acceptance criteria. TRIGGER when: (1) task has explicit files-to-modify and definition of done, (2) slice is single-role with no architectural uncertainty, (3) the mandatory architect decomposition gate has already been cleared for this task. SKIP: strategic decisions…
architect
Pre-task analysis and architecture design. TRIGGER for all tasks, without exception — mandatory gate before any sub-agent is spawned. Main Agent provides raw task description and codebase context; architect determines task boundaries and returns decomposition. SKIP: implementation, external technology research …
exa-researcher
Searches across Exa verticals — people, company, code, news. TRIGGER when: (1) task requires external information, competitive intelligence, or recent news, (2) finding code examples or library options. SKIP: internal codebase analysis (use architect), synthesis and recommendations (use analyst).
frontend-design
Production-grade UI implementation with high design quality. TRIGGER when: (1) building web components, pages, or dashboards, (2) styling or beautifying any web UI, (3) design brief is provided or inferable. SKIP: backend logic, data layer, tasks needing no UI output. Dashboards/web-UI overlap: frontend-design…
qa
Validates completed slices against acceptance criteria. TRIGGER when: (1) developer marks a slice devdone or readyforqa, (2) runtime or manual verification is required. SKIP: artifact-only or unit-only tasks (validator run / test suite serves as QA), tasks still inprogress.
security-reviewer
Performs security audits on code slices. TRIGGER when: requiressecurityreview is true, or task adds/modifies external inputs, auth flows, or third-party integrations. SKIP: internal refactors with no new attack surface — reports only, does not fix code.