autotask-mcp: Agent for Claude Code

.claude/agents/task-orchestrator.md

task-orchestrator is an agent for Claude Code from WYRE-AI/autotask-mcp. It costs 0 tokens per session (1,403 once invoked), scanned A, original, Apache-2.0.

An agent that coordinates work items in Task Master, a task-management system for software projects.

In plain words
What is it for?
Use it at the start of a work session and after tasks finish to assess the task queue and assign executable work.
Why use it?
It helps decide which tasks can run in parallel, which are blocked by dependencies, and when new work should begin.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

This is WYRE-AI/autotask-mcp's own configuration. It tells Claude Code how to work on autotask-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything autotask-mcp configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/WYRE-AI/autotask-mcp/main/.claude/agents/task-orchestrator.md
Clone the repo
git clone --depth 1 https://github.com/WYRE-AI/autotask-mcp

Made for: Claude Code.

Wrote 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.

agentmods badge for task-orchestrator

README.md
[![agentmods](https://agentmods.dev/badge/agents/wyre-ai/autotask-mcp/task-orchestrator.svg)](https://agentmods.dev/agents/wyre-ai/autotask-mcp/task-orchestrator)
Your own site
<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>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,403 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 8d ago against content hash 628c91991fef, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

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.

Origin

Copies of this mod

3 near-identical copies found in the catalogue:

.claude/agents/task-orchestrator.md · 131 lines

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

  1. 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.

  2. 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.

  3. 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.

  4. 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

  1. Use get_tasks or task-master list to retrieve all available tasks
  2. Analyze task statuses, priorities, and dependencies
  3. Identify tasks with status 'pending' that have no blocking dependencies
  4. Group related tasks that could benefit from specialized executors
  5. Create an execution plan that maximizes parallelization

Executor Deployment Phase

  1. 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
  2. Maintain a registry of active executors and their assigned tasks
  3. Establish communication protocols for progress updates

Coordination Phase

  1. Monitor executor progress through task status updates
  2. When a task completes:
    • Verify completion with get_task or task-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
  3. 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

Read the full file on GitHub · 131 lines

Changes

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.

  1. 8d ago First seen · 131 lines · 0 tokens per session scan A 628c91991fef

Subscribe to this mod's changes

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.

Related

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…

Apra-Labs/apra-fleet · 79 tokens

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.

The-AI-Directory-Company/agents-and-skills · 53 tokens

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.

The-AI-Directory-Company/agents-and-skills · 49 tokens

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.

The-AI-Directory-Company/agents-and-skills · 48 tokens

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.

TomMaSS/PRDforge · 52 tokens

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens