dispatch-manager

dispatch-manager is a skill for Claude Code, Codex from Justinmendezai/The-Adam-Repo. It costs 92 tokens per session (2,374 once invoked), scanned A, original, Apache-2.0.

A per-task coordinator that reads one task specification, prepares instructions for a coding agent, runs its check, and returns a short status line. A task specification is a document describing the work and how to verify it.

In plain words
What is it for?
Use it inside a larger build process when each task needs its own instructions, isolated coding agent, and verification step. It can also split an oversized task into smaller tasks.
Why use it?
It keeps each coordinator focused on one task and prevents unrelated task details from filling its working context.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents; mentions AGENTS.md.

Good fit Use it inside a larger build process when each task needs its own instructions, isolated coding agent, and verification step. It can also split an oversized task into smaller tasks.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/justinmendezai/the-adam-repo/dispatch-manager
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.

Any agent
npx skills add Justinmendezai/The-Adam-Repo --skill dispatch-manager
Clone the repo
git clone --depth 1 https://github.com/Justinmendezai/The-Adam-Repo

Made for: Claude Code, Codex.

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

agentmods badge for dispatch-manager

README.md
[![agentmods](https://agentmods.dev/badge/skills/justinmendezai/the-adam-repo/dispatch-manager/github.svg)](https://agentmods.dev/skills/justinmendezai/the-adam-repo/dispatch-manager)
Your own site
<a href="https://agentmods.dev/skills/justinmendezai/the-adam-repo/dispatch-manager"><img src="https://agentmods.dev/badge/skills/justinmendezai/the-adam-repo/dispatch-manager/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.

agentmods 80×15 button for dispatch-manager

Your own site · 80×15
<a href="https://agentmods.dev/skills/justinmendezai/the-adam-repo/dispatch-manager"><img src="https://agentmods.dev/badge/skills/justinmendezai/the-adam-repo/dispatch-manager.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 92 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,374 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.1 $0.00092 $0.02374
Opus 5 $0.00046 $0.01187
Sonnet 5 $0.00018 $0.00475
Haiku 4.5 $0.00009 $0.00237

Measured 12d ago against content hash d646c298d1fe, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

dispatch-manager 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 12d 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.

skills/dispatch-manager/SKILL.md · 209 lines

How it starts

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

dispatch-manager

The Tier-2 disposable manager. One slice in, one line out. The manager exists so the Tier-1 orchestrator never has to read a SPEC.md body — its entire context dies with this subagent when the slice finishes.

This skill is invoked by orchestrate-build. It is not invoked by the human directly; the human invokes the orchestrator and the orchestrator dispatches managers.

What this manager holds in context

  • Exactly one slices/<id>/SPEC.md.
  • slices/<id>/verify.sh (or the inline verify one-liner from the SPEC frontmatter).
  • plan/CONTEXT.md (one screen).
  • packet/PACKET.md success_criteria block only.
  • adam.json (runtime defaults).

Never in context:

  • Any other slice's spec.
  • Any other slice's tests.
  • The orchestrator's status registry.
  • orchestration-runs/.

Inputs (passed by the orchestrator as paths only)

slice_id:               <id>
spec_path:              slices/<id>/SPEC.md
verifier_path:          slices/<id>/verify.sh
context_path:           plan/CONTEXT.md
packet_path:            packet/PACKET.md
config_path:            adam.json
paths_out_of_scope:     <list of every other slice dir + packet/, plan/, agent-control/, orchestration-runs/, slices/<id>/SPEC.md, slices/<id>/tests/>

Workflow

1. Read the spec (and only the spec)

Read slices/<id>/SPEC.md. Note:

  • paths_in_scope (the only files the worker may write).
  • paths_out_of_scope from the spec (merge with the orchestrator's list).
  • Acceptance criteria.
  • Failing test paths the worker must turn green.
  • verify block — the runnable done-signal (a one-liner or a path to verify.sh).
  • Any sub_tasks: frontmatter block (see "Oversized slices" below).
  • human_gated: true flag, if present.

If the spec is missing any of these, return immediately:

blocked: <slice-id> reason=spec-missing-<field>

2. Build the worker prompt

Use the dispatch-builder template. Three additions specific to the manager hop:

Read the full file on GitHub · 209 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. 12d ago First seen · 209 lines · 92 tokens per session scan A d646c298d1fe

Subscribe to this mod's changes

dispatch-manager is a skill published in the GitHub repository Justinmendezai/The-Adam-Repo (12 stars, last pushed 18d ago), licensed Apache-2.0. It adds 92 tokens to every session and 2,374 once invoked, about $0.0005 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-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens