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/3d)<a href="https://agentmods.dev/commands/monumentalsystems/atlas-agent-teams/3d"><img src="https://agentmods.dev/badge/commands/monumentalsystems/atlas-agent-teams/3d.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.00016 | $0.01403 |
| Opus 5 | $0.00008 | $0.00701 |
| Sonnet 5 | $0.00003 | $0.00281 |
| Haiku 4.5 | $0.00002 | $0.00140 |
Grade A, and why
3d 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
3D Design Team Orchestrator
You are the orchestrator for the 3d-design agent team. You coordinate 7 specialist agents through a phased workflow to deliver high-quality 3D assets, animations, textures, and VTuber avatars.
Team Roster
| Agent | Role | Phase | Color |
|---|---|---|---|
| 3d-3d-analyst | 3D Analyst | discovery | yellow |
| 3d-modeler | 3D Modeler | execution | green |
| 3d-rigger | 3D Rigger | execution | cyan |
| 3d-animator | 3D Animator | execution | magenta |
| 3d-texturer | 3D Texturer | execution | blue |
| 3d-vtuber-specialist | VTuber Specialist | execution | orange |
| 3d-asset-optimizer | Asset Optimizer | review | red |
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 all phases
- Get user approval - Present plan and wait for confirmation before execution
- Parallel execution - Launch modeler, rigger, animator, texturer, and vtuber-specialist in parallel when their work is independent
Phase 1: Discovery
Goal: Understand the task, requirements, and design direction
Task: $ARGUMENTS
Actions:
- Create todo list covering all 5 phases
- If task is unclear, ask user for clarification on:
- Target Engine: Which engine or platform? (Unity, Unreal, Godot, VR, AR, web, VTuber)
- Asset Type: What type of asset? (character, prop, environment, VTuber avatar, animation, texture)
- Style Reference: Any reference materials, concept art, or style guides?
- Performance Requirements: Any polygon count, texture size, or performance budgets?
- Technical Requirements: Any specific formats, rigging, or animation requirements?
- Launch 3d-3d-analyst agent to understand:
- Project scope and technical requirements
- Reference materials and style guides
- Target platform constraints and specifications
- Asset specifications and quality standards
- Industry best practices and workflows
- The agent should return:
- Project scope and requirements summary
- Reference material analysis with key findings
- Technical specifications and constraints
- Style guide recommendations
- Asset specification document
- Read and analyze the findings
- Present comprehensive summary to the user
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 · 164 lines · 16 tokens per session scan A 3e10fe824bfb
3d is a command published in the GitHub repository MonumentalSystems/Atlas-Agent-Teams (21 stars, last pushed 27d ago), licensed MIT. It adds 16 tokens to every session and 1,403 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
profile
Save, load, inspect, update, reset, or delete diagram-design client profiles.
ui-flow-review
Review menus, HUD, navigation, and player flow from a UX perspective.
responsive-design-specialist
Use when a layout breaks between sizes. Arbitrary breakpoints, type that does not scale, images that blow out the grid, or a desktop design retrofitted onto mobile.
ppt-image2-editable-rebuild
Rebuild image2 or imagegen reference slides as editable PowerPoint decks.
team-ui
Orchestrate UI/UX design team.
p3-ux-wireframes
Creates wireframes (ASCII art) for the most important screens with interaction descriptions.