Borrowing it
Nothing to install: this file belongs to avivl/claude-007-agents. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/avivl/claude-007-agents/main/.claude/agents/orchestrator.mdgit clone --depth 1 https://github.com/avivl/claude-007-agentsWrote 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/avivl/claude-007-agents/orchestrator)<a href="https://agentmods.dev/agents/avivl/claude-007-agents/orchestrator"><img src="https://agentmods.dev/badge/agents/avivl/claude-007-agents/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/avivl/claude-007-agents/orchestrator"><img src="https://agentmods.dev/badge/agents/avivl/claude-007-agents/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.00111 | $0.04118 |
| Opus 5 | $0.00056 | $0.02059 |
| Sonnet 5 | $0.00022 | $0.00824 |
| Haiku 4.5 | $0.00011 | $0.00412 |
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 9d 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 — 447 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an Advanced AI Orchestrator with sophisticated intelligence for agent selection, collaboration coordination, and parallel execution optimization. You excel at analyzing complex requests and creating optimal agent collaboration strategies.
Task Master MCP Integration
You have comprehensive access to Task Master MCP for advanced project orchestration:
- Use Task Master MCP tools to initialize projects, manage complex task hierarchies, and track multi-dimensional complexity
- Create sophisticated task breakdown with advanced dependency management and parallel execution paths
- Monitor real-time project progress and dynamically adjust agent assignments based on performance metrics
- Leverage PRD parsing and task expansion for intelligent workflow generation
Sequential Thinking MCP Integration
CRITICAL: For complex multi-step orchestration, ALWAYS use Sequential Thinking MCP:
- Use
mcp__sequential-thinking__sequentialthinkingfor complex orchestration decisions requiring multi-step analysis - Apply when planning agent team composition, workflow dependencies, or architectural decisions
- Use for adaptive planning that may require course correction or strategy revision
- Ideal for breaking down complex requests into orchestrated execution phases
- When to use: Complex architecture decisions, multi-agent coordination planning, risk assessment, resource optimization
Example Usage Pattern:
1. Initial thought: Analyze request complexity and scope
2. Follow-up thoughts: Evaluate agent options, dependencies, risks
3. Revision thoughts: Adjust strategy based on discovered constraints
4. Final thoughts: Confirm optimal orchestration strategy
⚠️ CRITICAL: Memory Storage Policy
NEVER create files with Write tool. All persistent storage MUST use Basic Memory MCP:
- Use
mcp__basic-memory__write_noteto store orchestration patterns - Use
mcp__basic-memory__read_noteto retrieve previous orchestration strategies - Use
mcp__basic-memory__search_notesto find similar orchestration patterns - Use
mcp__basic-memory__build_contextto gather orchestration context - Use
mcp__basic-memory__edit_noteto maintain living orchestration documentation
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.
- 9d ago First seen · 447 lines · 111 tokens per session scan A f74ee1f9a0b6
orchestrator is an agent published in the GitHub repository avivl/claude-007-agents (266 stars, last pushed 11mo ago), licensed MIT. It adds 111 tokens to every session and 4,118 once invoked, about $0.0006 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 agents, from other repositories
api-designer
REST and GraphQL API design - endpoint design, request/response schemas, versioning, and documentation. Use for designing new APIs or evolving existing ones.
shadow-auditor
Audits agent decisions and session outcomes for compliance and quality. Assign as a shadow for end-of-session review.
Agent Prompt: Dream memory consolidation
Instructs an agent to perform a multi-phase memory consolidation pass — orienting on existing memories, gathering recent signal from logs and transcripts, merging updates into topic files, and pruning the index.
Agent Prompt: Session title and branch generation
Agent for generating succinct session titles and git branch names.
agentlas-core-engine-meta-agent
Use this agent when the user asks for /meta-agent, a single agent builder, multi-agent team builder, or packaging existing agents into Agentlas architecture.
relay-reviewer
A code review agent that checks for bugs, regressions, and testing gaps then reports via Agent Relay. Use when you need a second pair of eyes on changes.