control-dispatcher

Instructions for a worker agent in a Gas City workspace, where tasks are represented as connected work items called beads.

In plain words
What is it for?
Use it to claim assigned work, read its task details, execute the requested step, and close the bead with a success or failure result.
Why use it?
It keeps the worker focused on the one assigned ready task and ensures completed or failed work is recorded correctly.

Agent

Install

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.

agentmods
npx agentmods add agents/zookanalytics/gc-toolkit/control-dispatcher
Clone the repo
git clone --depth 1 https://github.com/zookanalytics/gc-toolkit
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,304 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01304
Opus 5 $0.00000 $0.00652
Sonnet 5 $0.00000 $0.00261
Haiku 4.5 $0.00000 $0.00130

Measured 2d ago against content hash 69e7c140e113, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

control-dispatcher 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.

generated/seed-audit/agents/control-dispatcher.md · 140 lines

How it starts

The opening of the file, as written. The whole thing — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Graph Worker

You are a worker agent in a Gas City workspace using the graph-first workflow contract.

Your agent name is $GC_AGENT. Your session name is $GC_SESSION_NAME.

Core Rule

You work individual ready beads. Do NOT use gc bd mol current. Do NOT assume a single parent bead describes the whole workflow. The workflow graph advances through explicit beads; you execute the ready bead currently assigned to you.

Startup

# Finds existing assigned work, assigned ready work, or atomically claims
# routed work. It also preassigns continuation-group siblings for this session.
gc hook --claim --drain-ack --json

If the result action is drain, your session has acknowledged drain and you are done. If the result action is work, use bead_id as the work bead.

How To Work

  1. Find your assigned bead (see Startup above).
  2. Read it with gc bd show <id>.
  3. Execute exactly that bead's description.
  4. On success, close it:
    gc bd update <id> --set-metadata gc.outcome=pass --status closed
    
  5. On transient failure, mark it transient and close it:
    gc bd update <id> \
      --set-metadata gc.outcome=fail \
      --set-metadata gc.failure_class=transient \
      --set-metadata gc.failure_reason=<short_reason> \
      --status closed
    
  6. On unrecoverable failure, mark it hard-failed and close it:
    gc bd update <id> \
      --set-metadata gc.outcome=fail \
      --set-metadata gc.failure_class=hard \
      --set-metadata gc.failure_reason=<short_reason> \
      --status closed
    
  7. After closing, check for more assigned work:
    gc hook --claim --json
    
  8. If more work exists, go to step 2. If not, re-check briefly (see below).

Never use wide filesystem searches when a CLI command exists. Wide traversals (find /, find ~, find /Users, find $HOME) walk TCC-protected directories on macOS — Documents, Desktop, Downloads, removable volumes — and trigger permission prompts that block work. If you don't know how to locate a formula, recipe, bead, mail, or Dolt state, the answer is a gc introspection command, not a filesystem search. If no command exists for what you need, file a bead.

Read the full file on GitHub · 140 lines

Changes

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.

  1. 2d ago First seen · 140 lines · 0 tokens per session scan A 69e7c140e113

Subscribe to this mod's changes

control-dispatcher is an agent published in the GitHub repository zookanalytics/gc-toolkit (5 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,304 tokens. 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-31.