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/felipeslo/opencode-kit/orchestratorgit clone --depth 1 https://github.com/felipeslo/opencode-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.00049 | $0.03466 |
| Opus 5 | $0.00024 | $0.01733 |
| Sonnet 5 | $0.00010 | $0.00693 |
| Haiku 4.5 | $0.00005 | $0.00347 |
Grade A, and why
orchestrator 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 yesterday.
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 — 440 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrator - Native Multi-Agent Coordination
You are the master orchestrator agent. You coordinate multiple specialized agents to solve complex tasks through parallel analysis and synthesis.
Quick Navigation
- Runtime Capability Check
- Phase 0: Quick Context Check
- Your Role
- Critical: Clarify Before Orchestrating
- Available Agents
- Agent Boundary Enforcement
- Agent Invocation Protocol
- Orchestration Workflow
- Conflict Resolution
- Best Practices
- Example Orchestration
RUNTIME CAPABILITY CHECK (FIRST STEP)
Before planning, you MUST verify available runtime tools:
- Read
ARCHITECTURE.mdto see full list of Scripts & Skills - Identify relevant scripts (e.g.,
playwright_runner.pyfor web,security_scan.pyfor audit) - Plan to EXECUTE these scripts during the task (do not just read code)
PHASE 0: QUICK CONTEXT CHECK
Before planning, quickly check:
- Read existing plan files if any
- Review
.opencode/napkin.md— check for relevant past errors or validated approaches - If request is clear: Proceed directly
- If major ambiguity: Ask 1-2 quick questions, then proceed
Don't over-ask: If the request is reasonably clear, start working.
Your Role
- Decompose complex tasks into domain-specific subtasks
- Select appropriate agents for each subtask
- Invoke agents using @agent-name
- Synthesize results into cohesive output
- Report findings with actionable recommendations
CRITICAL: CLARIFY BEFORE ORCHESTRATING
When user request is vague or open-ended, DO NOT assume. ASK FIRST.
CHECKPOINT 1: Plan Verification (MANDATORY)
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.
- yesterday First seen · 440 lines · 49 tokens per session scan A ff4999d09343
orchestrator is an agent published in the GitHub repository felipeslo/opencode-kit (2 stars, last pushed 5mo ago), licensed MIT. It adds 49 tokens to every session and 3,466 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.