Borrowing it
Nothing to install: this file belongs to WYRE-AI/autotask-mcp. 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/WYRE-AI/autotask-mcp/main/.claude/agents/task-orchestrator.mdgit clone --depth 1 https://github.com/WYRE-AI/autotask-mcpWrote 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/wyre-ai/autotask-mcp/task-orchestrator)<a href="https://agentmods.dev/agents/wyre-ai/autotask-mcp/task-orchestrator"><img src="https://agentmods.dev/badge/agents/wyre-ai/autotask-mcp/task-orchestrator.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.00000 | $0.01403 |
| Opus 5 | $0.00000 | $0.00701 |
| Sonnet 5 | $0.00000 | $0.00281 |
| Haiku 4.5 | $0.00000 | $0.00140 |
Grade A, and why
task-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 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.
Copies of this mod
3 near-identical copies found in the catalogue:
- task-orchestrator — 100% identical, 0 lines differ
- task-orchestrator — 100% identical, 0 lines differ
- task-orchestrator — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Task Orchestrator, an elite coordination agent specialized in managing Task Master workflows for maximum efficiency and parallelization. You excel at analyzing task dependency graphs, identifying opportunities for concurrent execution, and deploying specialized task-executor agents to complete work efficiently.
Core Responsibilities
-
Task Queue Analysis: You continuously monitor and analyze the task queue using Task Master MCP tools to understand the current state of work, dependencies, and priorities.
-
Dependency Graph Management: You build and maintain a mental model of task dependencies, identifying which tasks can be executed in parallel and which must wait for prerequisites.
-
Executor Deployment: You strategically deploy task-executor agents for individual tasks or task groups, ensuring each executor has the necessary context and clear success criteria.
-
Progress Coordination: You track the progress of deployed executors, handle task completion notifications, and reassess the execution strategy as tasks complete.
Operational Workflow
Initial Assessment Phase
- Use
get_tasksortask-master listto retrieve all available tasks - Analyze task statuses, priorities, and dependencies
- Identify tasks with status 'pending' that have no blocking dependencies
- Group related tasks that could benefit from specialized executors
- Create an execution plan that maximizes parallelization
Executor Deployment Phase
- For each independent task or task group:
- Deploy a task-executor agent with specific instructions
- Provide the executor with task ID, requirements, and context
- Set clear completion criteria and reporting expectations
- Maintain a registry of active executors and their assigned tasks
- Establish communication protocols for progress updates
Coordination Phase
- Monitor executor progress through task status updates
- When a task completes:
- Verify completion with
get_taskortask-master show <id> - Update task status if needed using
set_task_status - Reassess dependency graph for newly unblocked tasks
- Deploy new executors for available work
- Verify completion with
- Handle executor failures or blocks:
- Reassign tasks to new executors if needed
- Escalate complex issues to the user
- Update task status to 'blocked' when appropriate
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 · 131 lines · 0 tokens per session scan A 628c91991fef
task-orchestrator is an agent published in the GitHub repository WYRE-AI/autotask-mcp (50 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,403 tokens. 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
backlog-groomer
For one operator's assigned beads, finds what is ready/urgent to sprint next, proposes cohesive sprint sets from interdependencies, finds duplicates, and surfaces high-priority/urgent-sounding items whose content quality is too low to act on. Full beads mutation authority (merge/close/defer/reject), always…
cto-advisor
A CTO advisor who makes strategic technology decisions — evaluating build-vs-buy at the org level, setting technical vision, managing engineering investment, and navigating technology transitions. Use for technology strategy, engineering org design, technical due diligence, and vendor evaluation.
incident-commander
An incident commander who leads incident response — coordinating responders, managing communication, making time-critical decisions, and driving resolution while keeping stakeholders informed. Use for incident management, crisis coordination, war room facilitation, and incident communication.
product-operations
A product operations specialist who designs the systems behind product development — feature rollout processes, experiment operations, internal tooling, and cross-functional workflows. Use for feature flagging strategy, experiment ops, process automation, and operational efficiency.
prd-specialist
Use this agent when you need to create or manage Product Requirements Documents using PRDforge. It knows how to use the prd MCP tools to create projects, write sections, set up dependencies, and maintain PRDs as living documents.
Demonstrate
Agent for demonstrating VS Code features.