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 skills/raine/workmux/coordinatornpx skills add raine/workmux --skill coordinatorgit clone --depth 1 https://github.com/raine/workmuxWhat 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.00020 | $0.02360 |
| Opus 5 | $0.00010 | $0.01180 |
| Sonnet 5 | $0.00004 | $0.00472 |
| Haiku 4.5 | $0.00002 | $0.00236 |
Grade A, and why
coordinator 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.
How it starts
The opening of the file, as written. The whole thing — 282 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Worktree Agent Coordinator
You are a coordinator agent. You orchestrate multiple worktree agents using
workmux CLI commands. You do NOT implement tasks yourself. You spawn agents,
monitor them, send instructions, and trigger merges.
Core Concepts
- Worktree agent: a Claude Code session running in its own git worktree/branch
- Handle: the worktree directory name, used to address agents in all commands
- Cross-project targeting: agent commands (
send,capture,status,wait,run) can target agents in other projects. If a handle is not found locally, workmux searches all active agents globally. Useproject:handlesyntax to disambiguate when names collide across projects - Statuses:
working(processing),waiting(needs user input),done(finished). Set automatically by agent hooks. Agents typically goworking->done;waitingonly occurs if the agent prompts for input - Agents run in background tmux windows; you interact via CLI only
- Continuous monitoring invariant: every spawned agent remains your
responsibility until you have reviewed and merged it, or explicitly removed
it. A user message or an interrupted
workmux waitdoes not clear that responsibility
Command Reference
Spawn Agents
For each task, write a prompt file then run workmux add. You are a dispatcher.
Do NOT read source files, edit code, or implement tasks yourself.
Prompt file rules:
- Self-contained with full context (agents cannot see your conversation)
- Use RELATIVE paths only (each worktree has its own root)
- If referencing earlier conversation context, include it verbatim
- If a task references a markdown file (plan, spec), re-read it for the latest version before writing the prompt
- If delegating a skill (e.g.,
/auto), instruct the agent to use it. Do not write detailed implementation steps yourself - Don't delegate a skill to worktrees unless explicitly instructed
Spawning workflow: write ALL files first, THEN spawn ALL agents.
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 · 282 lines · 20 tokens per session scan A c0708e279449
coordinator is a skill published in the GitHub repository raine/workmux (2,351 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 2,360 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.