Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/sonichi/sutandonpx agentmods add skills/sonichi/sutando/worker-poolWrote 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/skills/sonichi/sutando/worker-pool)<a href="https://agentmods.dev/skills/sonichi/sutando/worker-pool"><img src="https://agentmods.dev/badge/skills/sonichi/sutando/worker-pool/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/skills/sonichi/sutando/worker-pool"><img src="https://agentmods.dev/badge/skills/sonichi/sutando/worker-pool.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.00017 | $0.02689 |
| Opus 5.5 | $0.00007 | $0.01076 |
| Sonnet 5.5 | $0.00003 | $0.00538 |
| Haiku 4.5 | $0.00002 | $0.00269 |
Grade A, and why
worker-pool 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 18d 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
worker-pool
Worker-pool commands live in scripts/; their suites live in
tests/skills/worker-pool/. The durable identity, routing, and delivery
contracts are in docs/worker-pool-design.md.
Modules (scripts/)
spawn_worker.py— mint a worker: identity records, delivery folder, tmux session, watcher; refuses before any side effect, rolls back on a launcher failure.create_worker.py— the one command that spawns and registers under the roster lock, so the roster cannot go stale.rename_worker.py— change a worker's base routing alias after creation:python3 skills/worker-pool/scripts/rename_worker.py --worker <id-or-label> --label "<new alias>" [--workspace W]. The id and its tmux session name stay.apply_profile_label_overrides.py— apply an AG2 Space profile's complete worker display-label map from JSON stdin with--workspace W --profile-mxid M --config-version N.worker_bootstrap.py— a worker session's first-turn decision (worker vs core mode) from its env.pool_roster.py— owner bindings + compiled roster;register_workeris the locked read-merge-write.worker_identity.py— worker / session / incarnation records.pool_router.py— resolve one task to its recipients from the roster.pool_route_handler.py— the core watcher's task-event handler (SUTANDO_TASK_EVENT_HANDLER): declines unbound work, delivers bound work as sentinels.pool_delivery.py— a recipient's own folder: sentinels in, accept, release, done flags.pool_ask.py— ask another instance a question through the front door (below).pool_sessions.py— read-only: which worker tmux sessions a viewer could attach, and the exact-match argv for each. Adds no state and nothing in the pool calls it; it exists for the desktop app's terminal picker. It deliberately does not describe the core, whose socket resolution belongs to the app.
python3 skills/worker-pool/scripts/pool_sessions.py list --workspace "$WS" [--room '!id:ag2.space']
What ships with it
29 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- scripts/apply_profile_label_overrides.py 1.6 KB runs code
- scripts/create_worker.py 9.9 KB runs code
- scripts/launch-codex-worker-session.sh 5.0 KB runs code
- scripts/launch-worker-session.sh 8.9 KB runs code
- scripts/pool_advertise.py 9.2 KB runs code
- scripts/pool_ask.py 9.7 KB runs code
- scripts/pool_attribution.py 3.3 KB runs code
- scripts/pool_beat.py 5.2 KB runs code
- scripts/pool_delivery.py 23 KB runs code
- scripts/pool_record.py 5.2 KB runs code
- scripts/pool_remedy_timer.py 12 KB runs code
- scripts/pool_remedy.py 25 KB runs code
- scripts/pool_roster.py 24 KB runs code
- scripts/pool_route_handler.py 10 KB runs code
- scripts/pool_router.py 14 KB runs code
- scripts/pool_routing_receipt.py 2.1 KB runs code
- scripts/pool_sessions.py 5.0 KB runs code
- scripts/pool_supervise.py 18 KB runs code
- scripts/pool_supervision.py 15 KB runs code
- scripts/pool_wedge_cards.py 12 KB runs code
- scripts/rename_worker.py 2.7 KB runs code
- scripts/resolve_inbox_entry.py 3.2 KB runs code
- scripts/resolve-inbox-entry 807 B
- scripts/spawn_worker.py 23 KB runs code
- scripts/worker_bootstrap.py 11 KB runs code
- scripts/worker_delivery.py 2.8 KB runs code
- scripts/worker_identity.py 13 KB runs code
- scripts/worker_picker_commands.py 17 KB runs code
- scripts/worker-watcher-supervisor.sh 4.6 KB runs code
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.
- 18d ago Changed · +14 lines 6a8bda9cfc02
- 19d ago Changed · +52 lines ed2caf4fad95
- 20d ago Changed · +6 lines · -13 tokens per session df41f1f2b915
- 21d ago Changed · +16 lines de0ddc66ea6a
- 23d ago Changed · +7 lines 736ad8c41075
- 25d ago Changed · +5 lines 900e9f254537
- 27d ago Changed · +38 lines 9aeb6f558988
- 1mo ago Changed · +15 lines 5cd19f7e3193
- 1mo ago First seen · 36 lines · 30 tokens per session scan A 3f60986896d4
worker-pool is a skill published in the GitHub repository sonichi/sutando (397 stars, last pushed today), licensed MIT. It adds 17 tokens to every session and 2,689 once invoked, about $0.0001 per session on Opus 5.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-09-13.
Other skills, from other repositories
app-builder
Build and edit small, personal visual tools and artifacts — dashboards, trackers, calculators, data visualizations, charts, simple landing pages, and slide decks the user wants for THEMSELVES. This is the right skill whenever the user asks to "visualize this," "make a chart," or "build an artifact" for their own use…
gmail
Manage Gmail email — drafting, sending, organizing, filters, vacation replies, and inbox analysis.
assistant-migration
Migrate from ChatGPT, Claude, OpenClaw, Hermes, Manus, and other AI assistants into Vellum by inspecting their data exports, conversation archives, files, prompts, custom instructions, memory, saved memories, tools, GPTs, workflows, integrations, and relationships, then mapping as much as safely possible into Vellum…
guardian-verify-setup
Set up channel verification for phone, Telegram, Slack, Discord, or email channels via outbound verification flow.
stripe-link-wallet
Agent wallet on the Stripe Link CLI (link-cli). Connect the wallet, then buy, purchase and pay for things on the user's behalf via approved spend requests, one-time-use cards, and 402 / Machine Payment Protocol (MPP) payments.
vellum-memory-v3-migration
One-time migration of an existing memory-v2 concept corpus into the memory-v3 section-grain "wiki" — topical articles with a stand-alone lead and queryable sections — with loss-proof staging, assistant-reviewed authoring, and a retrieval-eval gate before cutover.