autotask-mcp1: Agent for Claude Code

.claude/agents/task-orchestrator.md

task-orchestrator is an agent for Claude Code from haxos-anon/autotask-mcp1. It costs 0 tokens per session (1,403 once invoked), scanned A, a copy of task-orchestrator, Apache-2.0.

An agent for coordinating Task Master work, including assessing tasks, dependencies, parallel work, and executor deployment. Task dependencies are relationships that determine which work must happen first.

In plain words
What is it for?
Use it to review available tasks, identify parallelizable work, deploy task executors, and reassess the queue as tasks finish.
Why use it?
It helps organize complex task queues and decide what can be worked on at the same time.

Agent for Claude Code

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

This is haxos-anon/autotask-mcp1's own configuration. It tells Claude Code how to work on autotask-mcp1 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-mcp1 configures →

Reuse

Borrowing it

Nothing to install: this file belongs to haxos-anon/autotask-mcp1. 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/haxos-anon/autotask-mcp1/main/.claude/agents/task-orchestrator.md
Clone the repo
git clone --depth 1 https://github.com/haxos-anon/autotask-mcp1

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/haxos-anon/autotask-mcp1/task-orchestrator/github.svg)](https://agentmods.dev/agents/haxos-anon/autotask-mcp1/task-orchestrator)
Your own site
<a href="https://agentmods.dev/agents/haxos-anon/autotask-mcp1/task-orchestrator"><img src="https://agentmods.dev/badge/agents/haxos-anon/autotask-mcp1/task-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.

agentmods 80×15 button for task-orchestrator

Your own site · 80×15
<a href="https://agentmods.dev/agents/haxos-anon/autotask-mcp1/task-orchestrator"><img src="https://agentmods.dev/badge/agents/haxos-anon/autotask-mcp1/task-orchestrator.svg" alt="Reviewed on agentmods" width="80" 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 100% copy Near-identical to another mod 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-09, 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

This is a copy

100% identical to task-orchestrator — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.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 haxos-anon/autotask-mcp1 (0 stars, last pushed 4mo ago), 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. It is 100% identical to task-orchestrator, differing in 0 lines, and is treated as a copy.

Related

Other agents, from other repositories

project-implementer

Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.

athola/claude-night-market · 38 tokens

scrum-master

Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.

LuisFelipeMoro/Harness-devkit · 24 tokens

onboard-guide

Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.

smicolon/ai-kit · 46 tokens

jira-analyst

Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…

ngocsangyem/MeowKit · 72 tokens

pm-advisor

You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".

VandanaAjayDubey111/great-pm · 123 tokens

goals-onboarding

Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…

41fred/ace-level1 · 206 tokens