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 JustMichael-80/MasterVault --skill dispatching-parallel-agentsgit clone --depth 1 https://github.com/JustMichael-80/MasterVaultWrote 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/justmichael-80/mastervault/dispatching-parallel-agents)<a href="https://agentmods.dev/skills/justmichael-80/mastervault/dispatching-parallel-agents"><img src="https://agentmods.dev/badge/skills/justmichael-80/mastervault/dispatching-parallel-agents/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/justmichael-80/mastervault/dispatching-parallel-agents"><img src="https://agentmods.dev/badge/skills/justmichael-80/mastervault/dispatching-parallel-agents.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.00026 | $0.01494 |
| Opus 5.5 | $0.00010 | $0.00598 |
| Sonnet 5.5 | $0.00005 | $0.00299 |
| Haiku 4.5 | $0.00003 | $0.00149 |
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 1mo 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.
This is a copy
95% identical to dispatching-parallel-agents — 18 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dispatching Parallel Agents
Overview
You delegate tasks to specialized agents with isolated context. By precisely crafting their instructions and context, you ensure they stay focused and succeed at their task. They should never inherit your session's context or history — you construct exactly what they need. This also preserves your own context for coordination work.
When you have multiple unrelated failures (different test files, different subsystems, different bugs), investigating them sequentially wastes time. Each investigation is independent and can happen in parallel.
Core principle: Dispatch one agent per independent problem domain. Let them work concurrently.
When to Use
digraph when_to_use {
"Multiple failures?" [shape=diamond];
"Are they independent?" [shape=diamond];
"Single agent investigates all" [shape=box];
"One agent per problem domain" [shape=box];
"Can they work in parallel?" [shape=diamond];
"Sequential agents" [shape=box];
"Parallel dispatch" [shape=box];
"Multiple failures?" -> "Are they independent?" [label="yes"];
"Are they independent?" -> "Single agent investigates all" [label="no - related"];
"Are they independent?" -> "Can they work in parallel?" [label="yes"];
"Can they work in parallel?" -> "Parallel dispatch" [label="yes"];
"Can they work in parallel?" -> "Sequential agents" [label="no - shared state"];
}
Use when:
- 3+ test files failing with different root causes
- Multiple subsystems broken independently
- Each problem can be understood without context from others
- No shared state between investigations
Don't use when:
- Failures are related (fix one might fix others)
- Need to understand full system state
- Agents would interfere with each other
The Pattern
1. Identify Independent Domains
Group failures by what's broken:
- File A tests: Tool approval flow
- File B tests: Batch completion behavior
- File C tests: Abort functionality
Each domain is independent - fixing tool approval doesn't affect abort tests.
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.
- 1mo ago First seen · 186 lines · 26 tokens per session scan A f0df13f58404
dispatching-parallel-agents is a skill published in the GitHub repository JustMichael-80/MasterVault (12 stars, last pushed 2mo ago), licensed MIT. It adds 26 tokens to every session and 1,494 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to dispatching-parallel-agents, differing in 18 lines, and is treated as a copy.
Other skills, from other repositories
memorb-conventions
A set of base rules for organizing a memOrb vault, including paths, folders, names, YAML frontmatter, and orb layouts. YAML frontmatter is structured information placed at the top of a text file.
dream-studio
The dream studio: once a month, use the Memory Commit Journal in memorbs/log.md to select source orbs, find recurring themes, propose new Core orbs and new or revised Belief orbs, refresh the current-state narrative on each Island, and finally rotate the journal. Sole executor of Evaluate, the last step of the…
island-reclamation
The full procedure for adding an Island (a domain of long-term responsibility or interest): first agree with the user on what the Island is and at what level to name it, then pick a folder structure, then get the first batch of files confirmed — and only then create anything, finishing with a memory-layer sync.…
memorb-lint
Wiki Lint workflow: a health check over the memory vault that surfaces contradictions, stale pages, orphans, missing pages, broken wikilinks, and bare internal paths. Offer to run it before dream-studio or after manual moves/renames. Triggers: tidy up memory, check the second brain, health check, fix links, moved…
writing-memorb-skills
A meta-skill for creating or changing smaller skills in a shared collection, including their names, metadata, structure, registration, and tests.
memorb-domain-query
Use when querying companies, employees, or contacts by email address, domain name, or company name, or when integrating Outlook/M365 email collection and company email status checks.