team-dispatch

A team-dispatch skill that turns one plan phase into a clear assignment for a specialist subagent. The assignment includes the goal, completion checks, allowed tools, limits, and required return format.

In plain words
What is it for?
Use it to delegate a defined phase of a coding task, set what the subagent may access, and collect its summary, produced files, open questions, and suggested next phase.
Why use it?
It prevents agents from working toward vague or changing goals and gives the main agent a structured result it can log. Files are the shared record instead of an in-memory shared store.

Skill for Claude CodeCodex

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 skills/othmanadi/mddesign/team-dispatch
Any agent
npx skills add OthmanAdi/MDDesign --skill team-dispatch
Clone the repo
git clone --depth 1 https://github.com/OthmanAdi/MDDesign

Made for: Claude Code, Codex.

Per session 61 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,405 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.00061 $0.01405
Opus 5 $0.00030 $0.00702
Sonnet 5 $0.00012 $0.00281
Haiku 4.5 $0.00006 $0.00140

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

Security

Grade A, and why

team-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.

.clinerules/team-dispatch/SKILL.md · 129 lines

How it starts

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

Team Dispatch

Subagent dispatch arm. The PhaseSpec v1 contract is the only handoff format used between parent and child agents.

PhaseSpec v1 (the contract)

phase_id: <stable id, used as filename prefix and progress.md anchor>
parent_plan_ref: <pointer to task_plan.md#phase-N>
goal: <one sentence>
done_when:                       # testable exit criteria, no goalpost moving
  - <criterion 1>
  - <criterion 2>
inputs:
  files: [<read-only file refs>]
  memory_keys: [<keys for memory-layer recall>]
tools_allowed: [<list>]
tools_denied: [<list>]
budget:
  max_tool_calls: <int>
  max_wall_seconds: <int>
hitl_checkpoints: [<named checkpoint strings the child surfaces>]
return_contract:
  format: markdown+frontmatter
  fields: [summary, artifacts, open_questions, next_phase_hint]

Six load-bearing properties:

  1. parent_plan_ref is a pointer (file path with anchor), not a copy of the phase text. The child reads the file itself.
  2. done_when is testable. Without it, completion is hallucinatable.
  3. tools_allowed and tools_denied map onto the Claude Code permission model and any other framework's permission story.
  4. hitl_checkpoints are named strings the child surfaces by printing HITL_CHECKPOINT: <name> to stdout.
  5. return_contract forces structured output. The child returns markdown with frontmatter; the parent parses it deterministically.
  6. phase_id doubles as the filename prefix for any artifacts the child writes.

Available subagents

Each is defined as agents/<name>.md in this plugin.

Subagent When to pick
planner A phase exists in task_plan.md but has no PhaseSpec yet. The planner drafts one.
executor Default. A PhaseSpec exists; the work is straightforward; one specialist runs it end to end.
reviewer Auto-approve mode is on; we need a surrogate human to check the executor's return against done_when.
memory-keeper Stop hook fired; we need to classify session output into scratch/WHERE/WHY.
design-archeologist /mddesign:harvest invoked; long-running codebase scan needed.

Read the full file on GitHub · 129 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 · 129 lines · 61 tokens per session scan A e2a8984ec886

Subscribe to this mod's changes

team-dispatch is a skill published in the GitHub repository OthmanAdi/MDDesign (13 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 61 tokens to every session and 1,405 once invoked, about $0.0003 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.