__TEAM__-orchestrator

__TEAM__-orchestrator is an agent for Claude Code from MonumentalSystems/Atlas-Agent-Teams. It costs 25 tokens per session (265 once invoked), scanned A, original, MIT.

An orchestrator agent that leads a team of specialized agents through a coding task. It assigns work, coordinates dependencies, combines results, and checks quality.

In plain words
What is it for?
Use it to plan multi-agent repository work, assign tasks by specialization, integrate findings, and review the final result.
Why use it?
It helps divide a complex task into manageable parts while keeping the agents’ work consistent and identifying conflicts or risks.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter; names the TodoWrite tool.

Part of the __TEAM__ plugin — 1 skill, 1 command, 3 agents shipped together

Good fit Use it to plan multi-agent repository work, assign tasks by specialization, integrate findings, and review the final result.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/monumentalsystems/atlas-agent-teams/orchestrator
Install

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.

Clone the repo
git clone --depth 1 https://github.com/MonumentalSystems/Atlas-Agent-Teams

Made for: Claude Code.

Or install __TEAM__, the plugin that ships this one along with the rest of its 1 skill, 1 command, 3 agents.

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 __TEAM__-orchestrator

README.md
[![agentmods](https://agentmods.dev/badge/agents/monumentalsystems/atlas-agent-teams/orchestrator/github.svg)](https://agentmods.dev/agents/monumentalsystems/atlas-agent-teams/orchestrator)
Your own site
<a href="https://agentmods.dev/agents/monumentalsystems/atlas-agent-teams/orchestrator"><img src="https://agentmods.dev/badge/agents/monumentalsystems/atlas-agent-teams/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 __TEAM__-orchestrator

Your own site · 80×15
<a href="https://agentmods.dev/agents/monumentalsystems/atlas-agent-teams/orchestrator"><img src="https://agentmods.dev/badge/agents/monumentalsystems/atlas-agent-teams/orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 25 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 265 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.00025 $0.00265
Opus 5 $0.00013 $0.00133
Sonnet 5 $0.00005 $0.00053
Haiku 4.5 $0.00003 $0.00026

Measured 9d ago against content hash 4afb66006445, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

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

teams/_template/agents/orchestrator.md · 41 lines

What it actually says

You are the team lead for the TEAM agent team. You coordinate work across specialist agents and ensure high-quality delivery.

Core Mission

Manage the team workflow by:

  1. Understanding the task requirements
  2. Breaking work into agent-appropriate chunks
  3. Delegating to specialist agents
  4. Integrating their work products
  5. Ensuring quality and completeness

Coordination Approach

Task Decomposition

  • Read team.json to understand available agents and their roles
  • Match task requirements to agent specializations
  • Identify parallel vs sequential work
  • Define clear inputs and expected outputs for each agent

Quality Control

  • Verify agent outputs before integration
  • Check for conflicts between parallel agent work
  • Ensure conventions and patterns are followed
  • Flag issues that need user input

Output Guidance

Provide:

  • Task breakdown with agent assignments
  • Dependency graph between work items
  • Integration plan for combining agent outputs
  • Risk assessment and mitigation strategy
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. 9d ago First seen · 41 lines · 25 tokens per session scan A 4afb66006445

Subscribe to this mod's changes

__TEAM__-orchestrator is an agent published in the GitHub repository MonumentalSystems/Atlas-Agent-Teams (21 stars, last pushed 28d ago), licensed MIT. It adds 25 tokens to every session and 265 once invoked, about $0.0001 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.