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.
npx skills add keithhegit/ultra-orchestration --skill dispatch-and-trackgit clone --depth 1 https://github.com/keithhegit/ultra-orchestrationWrote 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/keithhegit/ultra-orchestration/dispatch-and-track)<a href="https://agentmods.dev/skills/keithhegit/ultra-orchestration/dispatch-and-track"><img src="https://agentmods.dev/badge/skills/keithhegit/ultra-orchestration/dispatch-and-track/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/keithhegit/ultra-orchestration/dispatch-and-track"><img src="https://agentmods.dev/badge/skills/keithhegit/ultra-orchestration/dispatch-and-track.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.00046 | $0.00352 |
| Opus 5.5 | $0.00018 | $0.00141 |
| Sonnet 5.5 | $0.00009 | $0.00070 |
| Haiku 4.5 | $0.00005 | $0.00035 |
Grade A, and why
dispatch-and-track 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 2mo 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.
What it actually says
Dispatch And Track
Use the plan to route work safely and keep the run ledger current.
In STRICT and STRICT_OPENSPEC, the ledger is mandatory. If ledger.json
cannot be initialized or updated by the host/script layer, stop with a blocker
instead of replacing it with a prose-only log.
Update
current_stagetask_statusdependencies_satisfiedretry_countsmax_retriesactive_write_locksblockerspending_reviewintegration_status- current
run_mode - current OpenSpec change and slice status when present
control_surface_usedintent for delivery
Rules
- Only treat a work package as runnable when its dependencies are satisfied.
- Parallelize only work packages with disjoint owned paths.
- If packages overlap, serialize them and record why.
- Record active write locks before execution starts.
- Allow one retry only for transient failures.
- Convert blockers into clear summaries with evidence and recommended next actions.
- Prefer host-script ledger updates over asking the model to rewrite the full ledger object.
- Require JSON or structured
AgentResultbefore marking work review-ready. - For
STRICT_OPENSPEC, update or propose OpenSpec-side slice status after each completed implementation slice.
Use the ledger shape in ../ultra-orchestrator/references/contracts.md.
What ships with it
1 file 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.
- 2mo ago First seen · 43 lines · 46 tokens per session scan A 6fe4849ac2fe
dispatch-and-track is a skill published in the GitHub repository keithhegit/ultra-orchestration (6 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 46 tokens to every session and 352 once invoked, about $0.0002 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-31.
Other skills, from other repositories
gsd-mempalace-capture
File a phase artifact into MemPalace; mirror decision facts into its temporal KG.
gsd-quick-batch
Batch several /skill:gsd-quick-shaped tasks together — planned, dispatched, and merged as one run.
gsd-map-codebase
Analyze codebase with parallel mapper agents to produce .planning/codebase/ documents.
gsd-workspace
Manage GSD workspaces — create, list, or remove isolated workspace environments.
gsd-inbox
Triage and review open GitHub issues and PRs against project templates and contribution guidelines.
gsd-manager
Interactive command center for managing multiple phases from one terminal.