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/ai-sdlc-framework/ai-sdlc/dispatch-workergit clone --depth 1 https://github.com/ai-sdlc-framework/ai-sdlcWhat 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.00191 | $0.04755 |
| Opus 5 | $0.00096 | $0.02377 |
| Sonnet 5 | $0.00038 | $0.00951 |
| Haiku 4.5 | $0.00019 | $0.00475 |
Grade A, and why
dispatch-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.
How it starts
The opening of the file, as written. The whole thing — 418 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run one in-session-agent Worker tick (RFC-0041 §4.3.1).
This command is the Worker half of the Conductor / Worker process split.
The operator opens one or more sibling Claude Code sessions and fires
/ai-sdlc dispatch-worker in each. Each session loops:
- Claim one manifest from the Dispatch Board.
- Invoke the
ai-sdlc:developersubagent in foreground. - Write the verdict to
done/(success) orfailed/(diagnostic). ScheduleWakeupfor the next tick.
When the queue is empty the session hibernates for ~30 seconds (configurable
via .ai-sdlc/dispatch-config.yaml spec.inSessionAgent.emptyQueueHibernateSec)
before re-polling — this avoids burning subscription tokens on busy-waits.
Worker isolation rationale
Workers run in their own Claude Code sessions and invoke Agent in
foreground. This isolation provides operator-controlled parallelism (N
sessions = N workers), explicit subscription-quota visibility, and
independence from the Conductor's session lifecycle.
Historical note (2026-05-21): RFC-0041 §2.1 originally cited Anthropic's
"600s silent-stdout background-agent watchdog (~85% kill rate during pnpm
test)" as the primary motivation for moving Workers out of the Conductor's
session. That claim was a misdiagnosis — forensic re-measurement of 73 dev
subagent transcripts via python3 ~/.claude/skills/audit-subagent/audit.py
found 0 watchdog-shape kills and 80.8% clean completion (median 16 min,
max 2.5 h). The 19.2% failures were operator-initiated interrupts, not
system kills. The Dispatch Board pattern stands on the other rationales
above; the watchdog-avoidance framing has been removed.
Hard rules (identical to /ai-sdlc execute)
- Never merge any PR. Do not run
gh pr merge. - Never force-push. Use
--force-with-leaseonly after the mandatory rebase. - Never close PRs or issues. No
gh pr close,gh issue close. - Never delete branches. No
git branch -D/-d. - Never edit
.ai-sdlc/**or.github/workflows/**. - Never run destructive git operations. No
git reset --hard. - Never write CI-skip tokens (
[skip ci],[ci skip], etc.) in commits.
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 · 418 lines · 191 tokens per session scan A 0a27360bfa22
dispatch-worker is a command published in the GitHub repository ai-sdlc-framework/ai-sdlc (92 stars, last pushed 8d ago), licensed Apache-2.0. It adds 191 tokens to every session and 4,755 once invoked, about $0.0010 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
discover
Discover runtime AI components and static AI dependencies with AIR Blackbox.
evidence
Export a signed compliance evidence package as JSON or PDF for regulatory handoff.
replay
Replay recorded AI traces to detect behavioral drift between model versions.
comply
Run a full EU AI Act compliance scan on your Python AI project.
OPSX: Fast Forward
Create a change and generate all artifacts needed for implementation in one go.
spec-intake
Execute the canonical workflow: .agent/workflows/spec-intake.md.