Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add melodic-software/claude-code-plugins/plugin install implementationWrote 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/melodic-software/claude-code-plugins/implement-dispatch)<a href="https://agentmods.dev/skills/melodic-software/claude-code-plugins/implement-dispatch"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/implement-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/melodic-software/claude-code-plugins/implement-dispatch"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/implement-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.00104 | $0.14990 |
| Opus 5.5 | $0.00042 | $0.05996 |
| Sonnet 5.5 | $0.00021 | $0.02998 |
| Haiku 4.5 | $0.00010 | $0.01499 |
Grade A, and why
implement-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 today.
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 — 299 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Arguments. [phase] [--items <path>] [--base <ref>] [--wave-cap <N>]. e.g., /implementation:implement-dispatch phase-2 --wave-cap 3, /implementation:implement-dispatch --items findings.md --base origin/integration/billing
Purpose
The orchestrated variant of /implementation:implement: same stage and plan, but the main window dispatches scope-fenced workers and verifies their returns instead of editing.
Gates
- One git writer per worktree, under either authority. A worktree has one index and one HEAD, so two workers staging or committing in it at once collide. Under
worker, where every worker stages and commits, rows that share a worktree run one at a time, whatever--wave-capallows. Concurrent rows in one worktree needorchestrator, where the orchestrator is the only git writer (see Concurrency). (A linked worktree shares "everything except per-worktree files such as HEAD, index", per https://git-scm.com/docs/git-worktree, verified 2026-09-27. Recheck when a git release note changes per-worktree state.) - Verify before accepting. Verify the return against direct evidence before accepting edits. Never accept a worker's green claim as the build signal; the orchestrator runs the build or
/toolchain:check. - Verify each phase before marking it
[DONE]: in every mode, dispatch the fresh-contextphase-verifierfor any phase beyond a mechanical, behavior-preserving change. A mechanical, behavior-preserving phase is the carve-out: withverify_mechanical_phasesresolvedfalse(the default), the orchestrator verifies it from the diff plus the build/test signal, and its fresh-context verdict is the PR's verify stage. Resolvedtruefrom any layer, the carve-out is off and the verifier runs for every phase. An orchestrator source commit made after the last phase's[DONE]is verified in every mode, with no mechanical exemption, before it is pushed or a PR is created. Both are defined under Phase boundaries. - Major divergence (fundamental assumption wrong) still STOPS even autonomously. Park the run with a handoff rather than improvising a new design.
- An
INCONCLUSIVEreturn, thephase-verifiercontract's answer when it could not decide every criterion, is not a verdict: the phase stays unmarked, and the orchestrator re-dispatches a fresh verifier against the gap the return named (narrower criteria, or the specific files it could not reach), never accepting the partial coverage and never marking[DONE]on it; a second inconclusive return on the same criteria is an escalation, handled like a divergence report. Surface subagent results in the response before ending the turn.
What ships with it
6 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.
- today Changed · +3 lines ad063520aaaf
- 3d ago Changed 06e13cd1d164
- 5d ago Changed · -112 lines · -2 tokens per session ba8f41a7aff2
- 6d ago Changed · +6 lines fee53fd594a7
- 7d ago Changed · +20 lines 3dd53130ae1a
- 8d ago Changed · +126 lines · +8 tokens per session 0cf2241c6af9
- 9d ago Changed · +1 lines c33e2a458a03
- 10d ago Changed · +5 lines 25e789476004
- 12d ago Changed 2e07be1e9b0f
- 13d ago First seen · 250 lines · 98 tokens per session scan A ff57089d1933
implement-dispatch is a skill published in the GitHub repository melodic-software/claude-code-plugins (26 stars, last pushed today), licensed MIT. It adds 104 tokens to every session and 14,990 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
parallel-orchestrator
Manage parallel Claude Code workstreams using git worktrees. Use when: splitting large tasks across multiple workers, coordinating parallel development, monitoring worker progress, integrating completed work, analyzing work item documents (code reviews, issue lists). Triggers: parallel, orchestrator, worktrees…
parallel-worker
Execute focused implementation tasks in a parallel workflow. Use when: working on assigned files in a worktree, making checkpoint commits, signaling dependencies or blockers, completing orchestrator-assigned tasks. Triggers: worker, checkpoint, worktree, assigned scope, commit prefix, parallel task.
optimize-local-search
For NP-hard optimization: TSP, scheduling, assignment problems. Uses greedy construction + local improvement (2-opt, hill climbing).
solve-constraint-puzzle
For constraint satisfaction: Sudoku, scheduling, N-queens, logic puzzles, SAT-like problems, assignment problems. Uses propagate-then-search pattern.
test-with-examples
For example-driven development: test cases as specifications, input/output pairs, documentation through examples.
return-none-for-failure
For graceful failure: return None or False instead of exceptions, let caller decide how to handle failure.