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 agentmods add skills/ibrahim-3d/orchestrator-supaconductor/dispatching-parallel-agentsnpx skills add Ibrahim-3d/orchestrator-supaconductor --skill dispatching-parallel-agentsgit clone --depth 1 https://github.com/Ibrahim-3d/orchestrator-supaconductorWrote 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/ibrahim-3d/orchestrator-supaconductor/dispatching-parallel-agents)<a href="https://agentmods.dev/skills/ibrahim-3d/orchestrator-supaconductor/dispatching-parallel-agents"><img src="https://agentmods.dev/badge/skills/ibrahim-3d/orchestrator-supaconductor/dispatching-parallel-agents.svg" alt="Measured on agentmods" 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 | $0.00026 | $0.01398 |
| Opus 5 | $0.00013 | $0.00699 |
| Sonnet 5 | $0.00005 | $0.00280 |
| Haiku 4.5 | $0.00003 | $0.00140 |
Grade A, and why
dispatching-parallel-agents 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 2d 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 2d ago First seen · 182 lines · 26 tokens per session scan A 403778edfc66
dispatching-parallel-agents is a skill published in the GitHub repository Ibrahim-3d/orchestrator-supaconductor (376 stars, last pushed 5mo ago), licensed AGPL-3.0. It adds 26 tokens to every session and 1,398 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-09-03.
Other skills, from other repositories
vertical-onboarding
Onboarding-and-switching playbook for SMB Product-Builder products. Defines the first-run experience that turns a prospect leaving an incumbent (ServiceTitan/Toast/Mindbody/Shopify/QuickBooks) into an activated user — import-first onboarding, the activation milestone, sample-data fallback, and the time-to-first-value…
parallel-session-coedit-via-source-mtime-and-idempotent-rebuild
Edit a shared deliverable while another live session or a colleague's agent is editing the same file right now — "don't delete each other's work", "only write when the other one is finished". When the file is built from many per item sources by an assembler (sections into one HTML, slides, reports): source mtime shows…
generate-daily-schedule
Use when turning a day's structured inputs — fixed commitments, tasks, and free windows — into a concrete 15-minute schedule. Domain-agnostic; the caller provides all context.
fan-out-cost-control
Dispatching a fan-out of agents: ban per-agent advisor() calls (check judgement once at the merge, not per shard), make agents append output as they go, and don't kill a fan-out past its costly stage — a killed agent returns nothing, a limit-killed one resumes from disk.
hato-cli
Send and receive messages between AI coding sessions with the hato CLI. Use when the user asks to message, ping, notify, or hand work to another session/agent/machine, when they mention hato, a post, a mailbox, or a bird name as a recipient, or when this session should watch for incoming messages. Works for any agent…
temporal
Help developers use Temporal for durable execution workflows. Covers CLI commands, SDK patterns (Go, TypeScript, Python, Java), workflow orchestration, and architectural decisions.