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/yves-s/just-ship/dispatching-parallel-agentsnpx skills add yves-s/just-ship --skill dispatching-parallel-agentsgit clone --depth 1 https://github.com/yves-s/just-shipWrote 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/yves-s/just-ship/dispatching-parallel-agents)<a href="https://agentmods.dev/skills/yves-s/just-ship/dispatching-parallel-agents"><img src="https://agentmods.dev/badge/skills/yves-s/just-ship/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.1 | $0.00026 | $0.01484 |
| Opus 5 | $0.00013 | $0.00742 |
| Sonnet 5 | $0.00005 | $0.00297 |
| Haiku 4.5 | $0.00003 | $0.00148 |
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 5d 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
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 5d ago First seen · 190 lines · 26 tokens per session scan A d9f241bd2c79
dispatching-parallel-agents is a skill published in the GitHub repository yves-s/just-ship (24 stars, last pushed 4mo ago), with no licence file. It adds 26 tokens to every session and 1,484 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-30.
Other skills, from other repositories
nazgul:start
Start or resume a Nazgul autonomous development loop. Use when user says "start nazgul", "run nazgul", "begin development", "resume the loop", or passes an objective for new work. Auto-detects project state — no arguments needed.
nazgul:init
Initialize Nazgul for a project — check prerequisites, run discovery, create runtime directories, generate reviewer agents. Use when setting up Nazgul for the first time, user says "initialize nazgul", "set up nazgul", or before running any other Nazgul commands.
nazgul:status
Check the current state of a Nazgul autonomous loop. Use when asked about loop progress, task status, iteration count, review board status, or how the Nazgul loop is going.
nazgul:complete
Close out an objective whose PR has already merged — ask the host whether it merged, record the merge evidence, and walk every stranded task to DONE through the sole sanctioned writer. Use when asked to close the objective, finish tasks after a merge, or when manifests are stuck at IMPLEMENTED or INREVIEW because the…
nazgul:config
View and change Nazgul settings — model assignments, formatter, notifications. Use when user says "configure nazgul", "change models", "nazgul settings", or wants to adjust config after init.
nazgul:log
View Nazgul run history — iteration timeline, task completions, review verdicts, git commits. Use after an overnight run to see what happened.