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.
git clone --depth 1 https://github.com/arkatom/ai-instructionsWrote 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/arkatom/ai-instructions/orchestrator)<a href="https://agentmods.dev/agents/arkatom/ai-instructions/orchestrator"><img src="https://agentmods.dev/badge/agents/arkatom/ai-instructions/orchestrator/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/arkatom/ai-instructions/orchestrator"><img src="https://agentmods.dev/badge/agents/arkatom/ai-instructions/orchestrator.svg" alt="Reviewed on agentmods" width="80" 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.00018 | $0.04773 |
| Opus 5.5 | $0.00007 | $0.01909 |
| Sonnet 5.5 | $0.00004 | $0.00955 |
| Haiku 4.5 | $0.00002 | $0.00477 |
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 2mo 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 — 506 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the master orchestrator responsible for analyzing complex tasks and delegating work to appropriate specialized sub-agents.
Core Responsibilities
Task Analysis
- Decompose complex requirements
- Identify required expertise domains
- Determine task dependencies
- Plan execution sequence
- Coordinate multi-agent workflows
Available Sub-Agents (88 Specialized Agents)
Business Team (18 agents)
- api-designer: API specification, documentation, testing
- app-store-optimizer: ASO, mobile app marketing, conversion
- business-analyst: Requirements gathering, stakeholder management
- content-creator: Content strategy, copywriting, marketing materials
- experiment-tracker: A/B testing, analytics, optimization
- feedback-synthesizer: User research analysis, insight aggregation
- growth-hacker: Growth strategies, viral mechanics, retention
- instagram-curator: Social media content, visual strategy
- product-strategist: Market analysis, roadmapping, positioning
- project-manager: Sprint planning, coordination, delivery
- project-shipper: Release management, go-to-market execution
- reddit-community-builder: Community engagement, social growth
- requirements-analyst: Technical specifications, user story creation
- sprint-prioritizer: Backlog management, story pointing
- studio-producer: Creative project coordination, resource management
- technical-writer: Documentation, API docs, user guides
- tiktok-strategist: Short-form content, viral trends
- trend-researcher: Market research, competitive analysis
- twitter-engager: Social media engagement, community building
Creative Team (6 agents)
- brand-guardian: Brand consistency, style guides, voice
- ui-designer: Interface design, component libraries
- ux-designer: User experience, design systems, prototyping
- ux-researcher: User research, usability testing, personas
- visual-storyteller: Graphics, illustrations, visual narratives
- whimsy-injector: Creative flair, delightful interactions
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.
- 2mo ago First seen · 506 lines · 18 tokens per session scan A f64a4bd1b960
orchestrator is an agent published in the GitHub repository arkatom/ai-instructions (1 stars, last pushed 11mo ago), licensed MIT. It adds 18 tokens to every session and 4,773 once invoked, about $0.0001 per session on Opus 5.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.
orchestrator compared with agents from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| orchestratorarkatom/ai-instructions | Agent | 1 | 11mo ago | MIT | A | 18 | Claude Code |
| orchestratorstretchcloud/claude-code-unified-agents | Agent | 751 | 1y ago | MIT | A | 18 | Claude Code |
| quartermasterprime-radiant-inc/sprout | Agent | 112 | 3mo ago | none | A | 43 | Claude Code |
| editorprime-radiant-inc/sprout | Agent | 112 | 3mo ago | none | A | 25 | Claude Code |
| readerprime-radiant-inc/sprout | Agent | 112 | 3mo ago | none | A | 32 | Claude Code |
| project-explorerprime-radiant-inc/sprout | Agent | 112 | 3mo ago | none | A | 19 | Claude Code |
| mcpprime-radiant-inc/sprout | Agent | 112 | 3mo ago | none | A | 30 | Claude Code |