Borrowing it
Nothing to install: this file belongs to friedbotstudio/baseline. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/friedbotstudio/baseline/main/.claude/skills/org-dispatch/SKILL.mdgit clone --depth 1 https://github.com/friedbotstudio/baselineWrote 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/friedbotstudio/baseline/org-dispatch)<a href="https://agentmods.dev/skills/friedbotstudio/baseline/org-dispatch"><img src="https://agentmods.dev/badge/skills/friedbotstudio/baseline/org-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/friedbotstudio/baseline/org-dispatch"><img src="https://agentmods.dev/badge/skills/friedbotstudio/baseline/org-dispatch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00143 | $0.01998 |
| Opus 5.5 | $0.00057 | $0.00799 |
| Sonnet 5.5 | $0.00029 | $0.00400 |
| Haiku 4.5 | $0.00014 | $0.00200 |
Grade A, and why
org-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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
org-dispatch — run an org-team over the coordination channel
org-dispatch is the execution engine of the org-team model: a flat pod of up to four peer Claude Code sessions claims lane-tagged slices of an approved spec and implements them concurrently over the baseline MCP channel, each peer in its own git worktree, so per-feature wall-clock approaches the slowest lane instead of the sum. It is the multi-session counterpart to swarm-dispatch (which parallelizes components of one spec inside one session via bounded subagents).
It is governed by Article X — Multi-session coordinated workflows (a different axis from Article II, which governs intra-session delegation and is untouched). The load-bearing difference from the retired sprint-dispatch sandbox: a peer decides its own in-lane implementation choices in its own main context — it does not bounce every fork to the lead. Only un-decidable or cross-lane forks escalate.
Gate: opt-in, off by default, git required
node .claude/skills/org-dispatch/org-mode.mjs gate # wraps org-mode.mjs -> orgDispatchGate
If the gate refuses, stop — org mode is the opt-in fence (and worktree isolation requires git).
The run loop (lead, in main context)
- Decompose into lanes. Read the approved spec and its dependency DAG. Each lane is one channel task
{id, lane, write_set, depends_on, assignee?}(org-mode.toLaneTasks). Write the tasks into the channel state and a durable plan (harness/plan-store.createPlan). A lane carries a domain tag the claiming peer inherits — its in-lane decision latitude. No sprint manifest is required: a lane is just a fully-specified task. The lead may alsoenqueue_taskad-hoc lanes at any time — peers can be handed tasks with no sprint in place; the pool is enabled byvelocity.org_mode.enabledalone. - Allocate: claim-any or directed. Leave a lane's
assigneeunset for claim-any (the first free peer wins) — simplest, but one fast peer can monopolize the queue while others idle. Setassigneeto apeer_idfor a directed lane that only that peer may claim — this is the lead's control to spread load across the pod or hand a specific lane to a named peer.claim_taskenforces it server-side (a non-assignee claim is rejected); thetask-availablepush carries the assignee so a well-behaved peer skips a lane that is not its own. - Select the pod (
peer-select.selectPeerClass): if human-launched peer sessions are registered on the channel, the flat pod (up to four) works the lanes; otherwise the lead spawns boundedswarm-workersubagents as the fallback execution surface. The lead is one of the four — flat for claiming, plus the arbitration + human-escalation hat. 3.5. Isolate every peer before any lane is claimed. For each peer, runworktree.createPeerWorktree({rootDir, peer_id}). It returns the peer's own working directory and branch (org/<peer_id>), or{ok: false, reason}. A refusal stops the dispatch — never fall back to running peers in the primary tree, because two peers in one checkout each see the other's half-finished edits as their own working tree, and the first commit carries both. Re-running for a peer that already has a tree returns the same path, so a resumed dispatch does not tear down live work.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 56 lines · 143 tokens per session scan A 5314336f00cc
org-dispatch is a skill published in the GitHub repository friedbotstudio/baseline (14 stars, last pushed 13d ago), licensed Apache-2.0. It adds 143 tokens to every session and 1,998 once invoked, about $0.0006 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
starting-a-new-project
Use when the workspace is empty, has no code, and the user brings a raw project idea. Normally reached via setting-up-a-project; not for an existing project.
customer-success
Support workflows, ticketing systems (Zendesk, Intercom), knowledge base design, chatbot design, and metrics (CSAT, NPS). Use when building support infrastructure, designing help centers, or optimizing customer experience.
event-planner
Event planning with timelines, budgets, vendor coordination, logistics checklists, and post-event evaluation. Use when organizing conferences, workshops, galas, or corporate events.
operations
Operations excellence expertise for supply chain optimization, process improvement (Lean, Six Sigma), capacity planning, vendor management, quality assurance, and operational efficiency. Use when optimizing processes, managing supply chains, or improving operational performance.
hr-talent
HR and talent management expertise for talent acquisition, performance management, compensation strategy, organizational design, culture building, succession planning, and D&I programs. Use when hiring, managing performance, designing organizations, or building culture.
innovation
Innovation management expertise for innovation frameworks (Design Thinking, Stage-Gate), ideation processes, innovation portfolio management, venture capital, open innovation, and IP strategy. Use when driving innovation, managing R&D portfolios, or building innovation programs.