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 commands/dwarvesf/dwarves-kit/dispatchgit clone --depth 1 https://github.com/dwarvesf/dwarves-kitWhat 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.00041 | $0.02341 |
| Opus 5 | $0.00020 | $0.01171 |
| Sonnet 5 | $0.00008 | $0.00468 |
| Haiku 4.5 | $0.00004 | $0.00234 |
Grade A, and why
dispatch 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a cross-goal dispatch lead. Your job is to take N independent specs, run the disjointness gate, fan out one isolated worktree worker per parallel-safe spec, collate their signals, and hand convergence to /kit:ship. You do NOT implement anything yourself and you NEVER auto-merge.
This is the kit's bounded concurrency surface (ADR-0019). It is cross-goal only: it never parallelizes one spec's tasks (/kit:execute stays sequential). The model is flat fan-out + a pairwise gate + a wait-queue, NOT a DAG. Dependent sub-goals that must be sequenced are /kit:mega territory; a real ordering graph (C needs A+B, then D needs C) is the handoff tripwire to GSD v2, not a reason to grow a scheduler here.
Prerequisites
- Each input spec is
Status: VALIDATEDand has a## Touchessection (directory-prefix globs). A spec lacking## Touchesis rejected by the gate (not assumed-empty). - The session runs under bypassPermissions (unattended workers cannot answer prompts; SPEC-032 DEC-009). Worker isolation rides on the worktree + the gate + the drift guard + the human-gated merge, NOT on per-command approval.
- Git working tree is clean (uncommitted changes would leak into worktrees).
If any prerequisite fails, say what is missing and stop.
Process
Step 1: Collect the dispatch-eligible specs
Take the specs named in the command argument, or if none given, list docs/specs/SPEC-*.md with Status: VALIDATED and a ## Touches section and ask the user which to dispatch. Show the set before going further.
Step 2: Run the disjointness gate (the moat)
bash lib/gate/dispatch-gate.sh plan <spec1> <spec2> ...
This prints one line per spec: PARALLEL <spec> (admitted to the concurrent set) or WAIT <spec> after <other> (overlaps an admitted spec; serialized into the wait-queue). The gate is conservative: any pair it cannot PROVE disjoint is serialized (over-serializing is safe-but-slower; merges are human-gated, so under-serializing is the only real danger and the gate structurally prevents it). A spec with no ## Touches makes the gate exit non-zero with a REJECT message; fix the spec, do not bypass the gate.
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 · 134 lines · 41 tokens per session scan A 2c50e3fe8245
dispatch is a command published in the GitHub repository dwarvesf/dwarves-kit (11 stars, last pushed 2d ago), licensed MIT. It adds 41 tokens to every session and 2,341 once invoked, about $0.0002 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 commands, from other repositories
OPSX: Archive
Archive a completed change in the experimental workflow.
OPSX: Explore
Enter explore mode - think through ideas, investigate problems, clarify requirements.
OPSX: Sync
Sync delta specs from a change to main specs.
OPSX: Propose
Propose a new change - create it and generate all artifacts in one step.
OPSX: Apply
Implement tasks from an OpenSpec change (Experimental).
OPSX: Update
Update a change - revise existing planning artifacts and keep them coherent (Experimental).