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/s3yed/appie-kit/dispatch-multiple-agentsnpx skills add S3YED/appie-kit --skill dispatch-multiple-agentsgit clone --depth 1 https://github.com/S3YED/appie-kitWhat 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.00033 | $0.00413 |
| Opus 5 | $0.00016 | $0.00206 |
| Sonnet 5 | $0.00007 | $0.00083 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
dispatch-multiple-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.
What it actually says
Dispatch Multiple Agents
When you have multiple independent tasks, don't do them sequentially. Dispatch agents to work in parallel.
When to Use
Use when:
- 3+ independent tasks need attention
- Tasks don't share state or resources
- No dependencies between tasks
- Speed matters
Don't use when:
- Tasks are related (fixing one might fix others)
- Tasks share files/resources (would conflict)
- You need full system context for all tasks
- Tasks must happen in specific order
The Pattern
1. Identify Independent Domains
Group work by what's needed:
- Task A: Research competitor A
- Task B: Research competitor B
- Task C: Research competitor C
Each is independent.
2. Create Focused Tasks
Each subagent gets:
- Specific scope: One clear task
- All context needed: Don't make them hunt
- Clear output: What should they return?
- Constraints: What NOT to touch
3. Dispatch in Parallel
Using sessions_spawn for concurrent execution.
4. Review and Integrate
When agents return:
- Read each result
- Verify no conflicts
- Integrate findings
- Report summary
Integration with Other Skills
Use dispatch-multiple-agents WITHIN the workflow:
brainstorming → write-plan → dispatch-multiple-agents → verify-task
↓
doing-tasks (per subagent)
Example
Problem: Research 5 competitors
Dispatch:
- Agent 1 → Competitor A
- Agent 2 → Competitor B
- Agent 3 → Competitor C
- Agent 4 → Competitor D
- Agent 5 → Competitor E
Result: Full analysis in minutes, not hours.
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 · 76 lines · 33 tokens per session scan A e2de84b7faa9
dispatch-multiple-agents is a skill published in the GitHub repository S3YED/appie-kit (6 stars, last pushed 6d ago), licensed MIT. It adds 33 tokens to every session and 413 once invoked, about $0.0002 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-31.
Other skills, from other repositories
agent-workflow-designer
Use when turning a business process into a multi-agent workflow with roles, tool permissions, human-review gates, and fallback.
model-selector
Use when the user needs to choose an LLM for a specific use case, weighing capability, cost, compliance, and latency.
adoption-roadmap
Use when the user needs a staged plan to take an LLM/agent from PoC to pilot to production.
setup
Activate for: configure agentic office, install agentic office, agentic office orientation, two-plugin architecture, create work.local, initialise workplace memory, agentic office getting started, configure agents, workplace configuration. NOT for: official productivity plugin setup (use /productivity:start).
skill-creator
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
mcporter
List, auth, and call MCP servers/tools from the terminal.