agentmods.dev

dispatch-codex

A command that sends a coding task to the Codex command-line tool through a planning, specification, and smoke-test workflow.

In plain words
What is it for?
Use it to force-dispatch a task when automatic dispatch would not start, then create a task specification and check the resulting API or UI output.
Why use it?
It gives tasks a fixed preparation and checking process, including required files, data, output shape, and limits before code is written.

Command

2 8d ago A scan 15 tokens original MIT
View the source file rhan1/crewline
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 commands/rhan1/crewline/dispatch-codex
Clone the repo
git clone --depth 1 https://github.com/rhan1/crewline
Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 443 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.00015 $0.00443
Opus 5 $0.00008 $0.00221
Sonnet 5 $0.00003 $0.00089
Haiku 4.5 $0.00002 $0.00044

Measured yesterday against content hash 202b2d67436b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

dispatch-codex scanned grade A with 1 finding 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 yesterday.

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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- UI component → dev server + browser/curl verification
commands/dispatch-codex.md · 32 lines

What it actually says

Run the Codex dispatch workflow for the task below, even if the auto-dispatch heuristics wouldn't have fired. Do NOT shortcut the spec-writing or smoke-test steps.

Task

$ARGUMENTS

Workflow

  1. Plan. Read the referenced files, pattern sources, and data endpoints yourself. If anything essential is missing (target path, output shape, data-source URL), ask before writing the spec — thin specs produce thin code.

  2. Write the spec to /tmp/codex-dispatch-<short-task-name>-<unix-ts>.txt. Cover:

    • Exact target file path
    • 2–3 pattern files to mirror (style + error-handling conventions)
    • Data sources and expected fields
    • Output shape (JSON for APIs, component signature for UI)
    • Explicit "do not do" constraints — no npm/git/vercel/deploy, no tests/READMEs, no modifying other files, no network validation

  3. Dispatch via ~/.claude/scripts/codex-dispatch.sh <spec-path> <short-task-name>. The wrapper runs codex exec, captures tokens/elapsed to ~/.claude/codex-last.json, and tees full log to ~/.claude/logs/codex-<ts>.log.

  4. Smoke-test the output before claiming success:

    • API handler → mock req/res Node harness against live data
    • UI component → dev server + browser/curl verification
    • Script → run against real input

  5. Fix small bugs directly (< 10 lines). Re-dispatch only if the change is substantial. If Codex fails or rate-limits, fall back to /dispatch-gemini or gemini --yolo -p "$(cat spec)".

  6. Report: what shipped, which bugs the smoke test caught, tokens used, wall-clock time, integration status.

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. yesterday First seen · 32 lines · 15 tokens per session scan A 202b2d67436b

Subscribe to this mod's changes

dispatch-codex is a command published in the GitHub repository rhan1/crewline (2 stars, last pushed 8d ago), licensed MIT. It adds 15 tokens to every session and 443 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Backend and APIsFrontendTesting
Related

Other commands, from other repositories

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

clarify

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

analyze

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

github/spec-kit · 26 tokens

converge

Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.

github/spec-kit · 35 tokens

implement

Execute the implementation plan by processing and executing all tasks defined in tasks.md.

github/spec-kit · 14 tokens