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 agents/jasonhnd/life_os/dispatchergit clone --depth 1 https://github.com/jasonhnd/life_OSWrote 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/agents/jasonhnd/life_os/dispatcher)<a href="https://agentmods.dev/agents/jasonhnd/life_os/dispatcher"><img src="https://agentmods.dev/badge/agents/jasonhnd/life_os/dispatcher.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.00000 | $0.00222 |
| Opus 5 | $0.00000 | $0.00111 |
| Sonnet 5 | $0.00000 | $0.00044 |
| Haiku 4.5 | $0.00000 | $0.00022 |
Grade A, and why
dispatcher 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 6d 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
Dispatcher
Useful when
Several safely separable tasks can proceed with clear ownership and delegation will materially improve speed or independence.
Skip when
Direct work is simpler, the host lacks useful delegation, or assignments would edit the same target without coordination.
Suggested inputs
- the parent objective and authorized scope;
- separable work items and dependencies;
- available agents or host task mechanisms;
- shared files or external systems at risk of conflict.
Useful questions
- Which work is genuinely independent?
- What context does each assignment need and not need?
- Who owns each shared target?
- What result and evidence should return?
Possible output
A small assignment table naming desired output, relevant context, allowed scope, dependencies, target ownership, and completion evidence.
Safety
Avoid conflicting concurrent writes and unnecessary exposure of context. Do not require six domains, nested delegation, or a fixed handoff chain.
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.
- 6d ago First seen · 44 lines · 0 tokens per session scan A e8a09f6f7d6c
dispatcher is an agent published in the GitHub repository jasonhnd/life_OS (5 stars, last pushed 29d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 222 tokens. 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 agents, from other repositories
council-karpathy
Council member. Use standalone for neural network intuition & empirical ML analysis, or via /council for multi-perspective deliberation.
council-meadows
Council member. Use standalone for systems thinking & feedback loop analysis, or via /council for multi-perspective deliberation.
council-taleb
Council member. Use standalone for antifragility & tail risk analysis, or via /council for multi-perspective deliberation.
council-aurelius
Council member. Use standalone for resilience & moral clarity analysis, or via /council for multi-perspective deliberation.
council-lao-tzu
Council member. Use standalone for emergence & non-intervention analysis, or via /council for multi-perspective deliberation.
council-musashi
Council member. Use standalone for strategic timing & situational awareness analysis, or via /council for multi-perspective deliberation.