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 instructions/nicogenti/opencode-orchestrator-kit/agents-mdgit clone --depth 1 https://github.com/NicoGenti/opencode-orchestrator-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.01432 | $0.01432 |
| Opus 5 | $0.00716 | $0.00716 |
| Sonnet 5 | $0.00286 | $0.00286 |
| Haiku 4.5 | $0.00143 | $0.00143 |
Grade A, and why
opencode-orchestrator-kit AGENTS.md 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.
How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Orchestration Framework
Overview
This document defines the strict orchestrator role for orchestrator and the contracts for all subagents. orchestrator MUST NOT perform direct work and MUST delegate all tasks to subagents based on their specialized roles.
Naming note: this file uses the same runtime
subagent_typeidentifiers defined inagents/orchestrator.md's routing table (profiler,explorer,librarian,oracle,planner,developer-fixer,test-engineer,code-reviewer,security,build-helper,npm-helper,deploy-helper,pc-doctor,writer). Earlier drafts of this framework used taxonomy-only placeholder names (sisyphus,explore,metis,momus,fixer,hephaestus, etc.) that have no corresponding runtime agent file — those names are retired. If you see them in older forks or notes, translate them using the table below.
Orchestrator: orchestrator
Role
- Strict Orchestrator:
orchestratoris the central coordinator and MUST NOT execute tasks directly. It MUST delegate all work to subagents. - Responsibilities:
- Analyze tasks and break them into subtasks.
- Select the appropriate subagent for each subtask, using the runtime IDs in
agents/orchestrator.md. - Enforce delegation policies (see Delegation Policies).
- Validate subagent outputs for completeness and correctness.
- Resolve conflicts or ambiguities between subagents.
- Ensure traceability and accountability for all delegated work (via
.context/*.mdandplan/*updates).
Delegation Policies
-
Mandatory Delegation:
orchestratorMUST delegate all executable tasks to subagents. It MUST NOT:- Write, edit, or refactor application code.
- Run tests or diagnostics.
- Perform research or analysis beyond task decomposition.
- Generate content (e.g., documentation, markdown, or prose) beyond its own three session-memory files.
-
Subagent Selection:
- Use the runtime roster below (and the full routing table in
agents/orchestrator.md) to match tasks to the most appropriate agent. - Prefer specialized subagents over general-purpose ones.
- Fall back to a higher-capability agent only if the primary subagent is unavailable or clearly insufficient.
- Use the runtime roster below (and the full routing table in
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 · 104 lines · 1,432 tokens per session scan A 53e7297c8d4c
opencode-orchestrator-kit AGENTS.md is an instructions file published in the GitHub repository NicoGenti/opencode-orchestrator-kit (5 stars, last pushed 2d ago), licensed MIT. It adds 1,432 tokens to every session, about $0.0072 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 instructions, from other repositories
agnix AGENTS.md
AGENTS.md instructions for agent-sh/agnix, covering project memory: agnix, project instruction files, critical rules, architecture and crate dependency graph.
ai-platform-engineering AGENTS.md
Instructions for caipe-io/ai-platform-engineering, covering agent instructions, project structure, find the canonical implementation, documentation and docs & spec rules.
cc-pocket AGENTS.md
Instructions for heypandax/cc-pocket, covering agents.md — cc-pocket, ⚠️ 本机 daemon 操作铁律（最重要，先读这一段）, 改完 daemon 代码要更新本机 daemon —— 只用这一条命令, 绝对不要做（每一条都会制造第二个 daemon → 立刻不可用） and 必须知道的两个反直觉事实（本机环境）.
spellbook AGENTS.md
Instructions for majiayu000/spellbook, covering spellbook agent contract, routing, scope rules, threads long-run guardrails and validation.
taskflow AGENTS.md
Instructions for heggria/taskflow, covering agents.md, project overview, architecture, key concepts and phase types (12 total).
AGI-Super-Team AGENTS.md
Instructions for aAAaqwq/AGI-Super-Team, a project described as: An installable, cross-framework AI organization: C-suite agents, expert subagents, curated skills, independent review, and one-command setup across 18 AI client/runtime adapters.