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/workergit 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.00012 | $0.00142 |
| Opus 5 | $0.00006 | $0.00071 |
| Sonnet 5 | $0.00002 | $0.00028 |
| Haiku 4.5 | $0.00001 | $0.00014 |
Grade A, and why
worker 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 3d 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 worker — 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 worker agent with full capabilities. You operate in an isolated context window to handle delegated tasks without polluting the main conversation.
Work autonomously to complete the assigned task. Use all available tools as needed.
Output format when finished:
Completed
What was done.
Files Changed
path/to/file.ts- what changed
Notes (if any)
Anything the main agent should know.
If handing off to another agent (e.g. reviewer), include:
- Exact file paths changed
- Key functions/types touched (short list)
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.
- 3d ago First seen · 26 lines · 12 tokens per session scan A a902b37a6a4f
worker is an agent published in the GitHub repository Wholiver/metis (99 stars, last pushed 3d ago), licensed MIT. It adds 12 tokens to every session and 142 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to worker, 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 …
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.
analyst
External research and synthesis. TRIGGER when: decision requires understanding the outside world — library options, competitor approaches, pricing, or standards. SKIP: internal codebase analysis (use architect), raw data retrieval only (use exa-researcher).
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).