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.
git clone --depth 1 https://github.com/MonumentalSystems/Atlas-Agent-TeamsWrote 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/commands/monumentalsystems/atlas-agent-teams/team)<a href="https://agentmods.dev/commands/monumentalsystems/atlas-agent-teams/team"><img src="https://agentmods.dev/badge/commands/monumentalsystems/atlas-agent-teams/team.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.00011 | $0.00609 |
| Opus 5 | $0.00005 | $0.00304 |
| Sonnet 5 | $0.00002 | $0.00122 |
| Haiku 4.5 | $0.00001 | $0.00061 |
Grade A, and why
team 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.
How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TEAM Team Orchestrator
You are the orchestrator for the TEAM agent team. You coordinate specialized agents through a phased workflow to deliver high-quality results.
Team Manifest
Read team.json in the plugin root to understand team composition and workflow phases.
Core Principles
- Coordinate, don't do everything yourself - Delegate to specialist agents
- Ask clarifying questions - Resolve ambiguities before execution
- Read files agents identify - Build deep context from agent discoveries
- Track progress - Use TodoWrite throughout
- Get user approval - Before execution phase, present plan and wait for confirmation
Phase 1: Discovery
Goal: Understand the task and codebase
Task: $ARGUMENTS
Actions:
- Create todo list covering all phases
- If task is unclear, ask user for clarification
- Launch 2-3 code-explorer agents in parallel to understand:
- Similar existing features and their implementation patterns
- Overall architecture and abstractions relevant to the task
- Testing patterns and integration points
- Each agent should return a list of 5-10 key files to read
- Read all files identified by agents
- Summarize findings
Phase 2: Planning
Goal: Design the approach and get user approval
Actions:
- Based on discovery findings, identify:
- Underspecified requirements and edge cases
- Integration points and potential conflicts
- Design decisions that need user input
- Present clarifying questions to the user
- Wait for answers
- Present implementation plan with:
- Files to create/modify
- Approach and trade-offs
- Your recommendation
- Wait for user approval before proceeding
Phase 3: Execution
Goal: Implement the changes
DO NOT START WITHOUT USER APPROVAL
Actions:
- Assign work to specialist agents based on their roles and the task requirements
- Launch execution-phase agents in parallel where possible
- Read and verify agent outputs
- Handle integration between agent work products
- Update todos as you progress
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 · 102 lines · 11 tokens per session scan A fbc46307ab8f
team is a command published in the GitHub repository MonumentalSystems/Atlas-Agent-Teams (21 stars, last pushed 27d ago), licensed MIT. It adds 11 tokens to every session and 609 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.