Borrowing it
Nothing to install: this file belongs to JosephOIbrahim/Hanna. 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/JosephOIbrahim/Hanna/main/.claude/commands/hanna-dispatch-next.mdgit clone --depth 1 https://github.com/JosephOIbrahim/HannaWrote 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/commands/josephoibrahim/hanna/hanna-dispatch-next)<a href="https://agentmods.dev/commands/josephoibrahim/hanna/hanna-dispatch-next"><img src="https://agentmods.dev/badge/commands/josephoibrahim/hanna/hanna-dispatch-next/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/commands/josephoibrahim/hanna/hanna-dispatch-next"><img src="https://agentmods.dev/badge/commands/josephoibrahim/hanna/hanna-dispatch-next.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.00022 | $0.01316 |
| Opus 5 | $0.00011 | $0.00658 |
| Sonnet 5 | $0.00004 | $0.00263 |
| Haiku 4.5 | $0.00002 | $0.00132 |
Grade A, and why
hanna-dispatch-next 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 9d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
hanna-dispatch-next
You are the harness for the Hanna buildout. This slash command advances the project by one lane per invocation, reading the single-source-of-truth status table in docs/ROADMAP.md §5 and dispatching the topmost unblocked lane per the MoE methodology ratified in docs/DECISIONS.md D002.
Protocol
-
Read
docs/ROADMAP.mdentirely. Pay particular attention to §4 (per-lane spec) and §5 (lane status table). -
Identify the next lane. Scan §5 top-to-bottom. The next lane is the topmost row where
Status == queuedAND every dependency lane (named in theUnblockscolumns of upstream rows, OR explicitly in §4 "Dependencies") hasStatus == done. -
If no lane is unblocked:
- All lanes done → report "All lanes complete; Hanna buildout is finished. Run
/hanna-buildout-status(future) or read NEXT.md for what's next." - Some queued but dependencies missing → report the dependency state and stop.
- Stop without dispatching.
- All lanes done → report "All lanes complete; Hanna buildout is finished. Run
-
If the lane is main-thread (per D002, substrate-decision class — currently L1 D008 propagation):
- Execute the work directly per the §4 brief skeleton for that lane.
- Verify completion criteria from §4.
- Update §5 status table from
queued→doneand record the new commit SHA in theLast commitcolumn. - Commit + push.
- Report the lane's completion + the next unblocked lane.
-
If the lane is MoE-eligible:
- Read §4 for that lane's brief skeleton.
- Dispatch the named expert(s) in parallel per D002 step 2, using the brief skeleton verbatim with any per-invocation specialization.
- After all builder experts return, dispatch the Compliance Reviewer alone per D002 step 4.
- Apply reviewer RECOMMENDED-CHANGES via Edit; re-dispatch any FAIL'd builder.
- Verify completion criteria from §4 (pytest counts, grep results, brief artifacts).
- Update §5 status table from
queued→doneand record the new commit SHA. - Commit (single commit per D002 step 6); push.
- Report the lane's completion + the next unblocked lane.
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.
- 9d ago First seen · 92 lines · 22 tokens per session scan A bf656c7182a4
hanna-dispatch-next is a command published in the GitHub repository JosephOIbrahim/Hanna (2 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 22 tokens to every session and 1,316 once invoked, about $0.0001 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.
Other commands, from other repositories
deps-audit
Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.
README
Git workflow and quality assurance commands for the claude-skills repository.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
growth-seo
SEO audit and optimization for organic search ranking.
wcag-audit
Accessibility audit based on WCAG 2.1/2.2 and the axe-core reference.