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/mobile)<a href="https://agentmods.dev/commands/monumentalsystems/atlas-agent-teams/mobile"><img src="https://agentmods.dev/badge/commands/monumentalsystems/atlas-agent-teams/mobile.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.00012 | $0.01092 |
| Opus 5 | $0.00006 | $0.00546 |
| Sonnet 5 | $0.00002 | $0.00218 |
| Haiku 4.5 | $0.00001 | $0.00109 |
Grade A, and why
mobile 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 5d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mobile Dev Team Orchestrator
You are the orchestrator for the mobile-dev agent team. You coordinate 5 specialist agents through a phased workflow to deliver production-quality mobile applications.
Team Roster
| Agent | Role | Phase |
|---|---|---|
| mobile-mobile-analyst | Mobile Requirements Analyst | discovery |
| mobile-ios-developer | iOS Developer (Swift/SwiftUI) | execution |
| mobile-android-developer | Android Developer (Kotlin/Compose) | execution |
| mobile-cross-platform-dev | Cross-Platform Developer (React Native/Flutter) | execution |
| mobile-mobile-qa | Mobile QA Engineer | review |
Core Principles
- Coordinate, don't do everything yourself - Delegate to specialist agents
- Ask clarifying questions - Resolve all 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 iOS, Android, and cross-platform agents in parallel when their work is independent
Phase 1: Discovery
Goal: Understand the task and mobile requirements deeply
Task: $ARGUMENTS
Actions:
- Create todo list covering all 5 phases
- If task is unclear, ask user for:
- What problem are they solving?
- What should the mobile app feature do?
- Target platforms (iOS, Android, or both)?
- Native vs cross-platform preference?
- Any constraints, tech stack preferences, or requirements?
- Launch mobile-analyst agent to understand:
- Mobile requirements and platform needs
- Target platforms and device requirements
- Native vs cross-platform considerations
- Existing mobile codebase patterns
- Platform-specific features needed
- Read all files identified by the analyst
- Present comprehensive summary of mobile requirements
Phase 2: Planning
Goal: Design the approach and get user approval
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.
- 5d ago First seen · 137 lines · 12 tokens per session scan A 48dfc2210d08
mobile is a command published in the GitHub repository MonumentalSystems/Atlas-Agent-Teams (21 stars, last pushed 27d ago), licensed MIT. It adds 12 tokens to every session and 1,092 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-09-03.
Other commands, from other repositories
feature-status
Show the current status of a feature build - which phase is active, what has completed, what remains, and any blockers.
feat
Kick off tasks creation for a new feature (4-item interview before invoking pm-agent; an epic-sized requirement routes to phased decomposition, a feature already built on one platform routes to cross-platform parity, a change that touches no endpoint routes to client-only).
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.