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 DavidROliverBA/ArchitectKB --skill orchestration-templategit clone --depth 1 https://github.com/DavidROliverBA/ArchitectKBWrote 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/davidroliverba/architectkb/orchestration-template)<a href="https://agentmods.dev/skills/davidroliverba/architectkb/orchestration-template"><img src="https://agentmods.dev/badge/skills/davidroliverba/architectkb/orchestration-template.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.00027 | $0.00904 |
| Opus 5 | $0.00014 | $0.00452 |
| Sonnet 5 | $0.00005 | $0.00181 |
| Haiku 4.5 | $0.00003 | $0.00090 |
Grade A, and why
orchestration-template 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sub-Agent Orchestration Template
This is a reference template for creating skills that use parallel sub-agents. It is NOT directly invocable - use it as a pattern when building new orchestrated skills.
When to Use This Pattern
Use sub-agent orchestration when:
- Task has 3+ independent research phases
- Each phase can run in parallel without dependencies
- Results need synthesis into a unified output
- Context isolation improves quality (prevents contamination)
Do NOT use when:
- Task is simple and linear
- Phases depend on each other sequentially
- Interactive dialogue is needed throughout
Orchestration Structure
Phase 1: Planning
1. TaskCreate for overall work item
2. Identify independent workstreams
3. Create sub-tasks for each workstream
4. Set dependencies with TaskUpdate (addBlockedBy)
Phase 2: Parallel Execution
Launch N agents in parallel using Task tool:
Task tool calls (in single message for parallelism):
Agent 1: subagent_type: "Explore", model: "haiku"
- Purpose: [specific research goal]
- Tools: Read, Glob, Grep (read-only)
Agent 2: subagent_type: "Explore", model: "haiku"
- Purpose: [different research goal]
- Tools: Read, Glob, Grep (read-only)
Agent 3: subagent_type: "general-purpose"
- Purpose: [complex analysis requiring writes]
- Tools: All available
Phase 3: Synthesis
1. Collect results from all agents
2. Identify conflicts or gaps
3. Generate unified output
4. Update tasks to completed
Model Selection for Sub-Agents
| Sub-Agent Purpose | Model | Rationale |
|---|---|---|
| Read-only search/exploration | Haiku | Fast, cheap, isolated context |
| Analysis with context | Sonnet | Good reasoning |
| Complex synthesis | Sonnet | Balanced cost/quality |
| Deep architecture reasoning | Opus | Extended thinking needed |
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.
- 8d ago First seen · 139 lines · 27 tokens per session scan A 651da4c62dc0
orchestration-template is a skill published in the GitHub repository DavidROliverBA/ArchitectKB (52 stars, last pushed 6mo ago), licensed MIT. It adds 27 tokens to every session and 904 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…