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/mattwynne/yaks/workergit clone --depth 1 https://github.com/mattwynne/yaksWhat 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.00145 |
| Opus 5 | $0.00006 | $0.00072 |
| Sonnet 5 | $0.00002 | $0.00029 |
| Haiku 4.5 | $0.00001 | $0.00015 |
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 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.
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.
- 2d ago First seen · 25 lines · 12 tokens per session scan A 5fe876851644
worker is an agent published in the GitHub repository mattwynne/yaks (56 stars, last pushed 21d ago), licensed MIT. It adds 12 tokens to every session and 145 once invoked, about $0.0001 per session on Opus 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-08-30.
Other agents, from other repositories
pi
OpenAgents supports Pi, Earendil's coding agent for the terminal — executable pi, distributed as the npm package @earendil-works/pi-coding-agent.
nanoclaw
NanoClaw lets a NanoClaw Agent Group act as an OpenAgents Workspace agent. Unlike most OpenAgents agents, NanoClaw is not a stdin/stdout CLI and not a direct LLM API — it is an independent containerized agent runtime. Each Agent Group runs in its own Docker container (Apple Container on macOS; WSL2 on Windows), with…
deepseek
DeepSeek's open-source agent harness run as an OpenAgents agent. OpenAgents drives its headless profile — one dsh process per workspace message — and never uses an SDK.
codebuddy
CodeBuddy Code — Tencent's terminal agent, installed as @tencent-ai/codebuddy-code — run as an OpenAgents agent.
github-copilot-cli
OpenAgents supports GitHub's official Copilot CLI — the standalone executable copilot, distributed as the npm package @github/copilot.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.