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 skills add OthmanAdi/MDDesign --skill team-dispatchgit clone --depth 1 https://github.com/OthmanAdi/MDDesignWrote 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/othmanadi/mddesign/team-dispatch)<a href="https://agentmods.dev/skills/othmanadi/mddesign/team-dispatch"><img src="https://agentmods.dev/badge/skills/othmanadi/mddesign/team-dispatch/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/othmanadi/mddesign/team-dispatch"><img src="https://agentmods.dev/badge/skills/othmanadi/mddesign/team-dispatch.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.00061 | $0.01405 |
| Opus 5.5 | $0.00024 | $0.00562 |
| Sonnet 5.5 | $0.00012 | $0.00281 |
| Haiku 4.5 | $0.00006 | $0.00140 |
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 1mo 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 — 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:
parent_plan_refis a pointer (file path with anchor), not a copy of the phase text. The child reads the file itself.done_whenis testable. Without it, completion is hallucinatable.tools_allowedandtools_deniedmap onto the Claude Code permission model and any other framework's permission story.hitl_checkpointsare named strings the child surfaces by printingHITL_CHECKPOINT: <name>to stdout.return_contractforces structured output. The child returns markdown with frontmatter; the parent parses it deterministically.phase_iddoubles 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. |
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.
- 1mo ago First seen · 129 lines · 61 tokens per session scan A e2a8984ec886
team-dispatch is a skill published in the GitHub repository OthmanAdi/MDDesign (14 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 61 tokens to every session and 1,405 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
workflow
Starts and manages autonomous agent workflows. Triggers: workflow, start workflow, autonomous agents, agent pipeline.
autonomous-dev
Drives a brief, specification, issue or existing PR through implementation, review, tests and QA to a ready PR. Persists ownership, progress and commit-bound evidence for safe resumption. Use for autonomous software delivery or finishing an interrupted development run.
onboard
Sets up ai-toolkit in a project: symlinks, CLAUDE.md, intent interview. Triggers: onboard, setup project, install ai-toolkit, migrate project.
plan
Breaks features/goals into phased plans with task lists, agent assignments, dependencies. Triggers: plan feature, implementation roadmap, break down task, project phases.
prd-to-issues
Splits a PRD into vertical-slice GitHub issues with HITL/AFK tagging and dependencies. Triggers: PRD to issues, create tickets, break down PRD, work items.
prd-to-plan
Converts PRD into phased plan via tracer-bullet vertical slices. Triggers: PRD to plan, break down PRD, implementation plan, tracer bullets, phased plan.