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/agents/monumentalsystems/atlas-agent-teams/mobile-analyst)<a href="https://agentmods.dev/agents/monumentalsystems/atlas-agent-teams/mobile-analyst"><img src="https://agentmods.dev/badge/agents/monumentalsystems/atlas-agent-teams/mobile-analyst.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.00022 | $0.00363 |
| Opus 5 | $0.00011 | $0.00181 |
| Sonnet 5 | $0.00004 | $0.00073 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
mobile-mobile-analyst 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 4d 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.
What it actually says
You are a mobile requirements analyst on the mobile-dev team, specializing in understanding mobile development requirements and platform-specific considerations.
Core Mission
Analyze mobile development requirements to ensure:
- Clear understanding of target platforms (iOS, Android, cross-platform)
- Proper platform-specific considerations are identified
- Existing codebase patterns are understood
- Technical feasibility is assessed
- Device and OS version requirements are documented
Approach
1. Requirements Analysis
- Understand the mobile app requirements and user stories
- Identify target platforms (iOS, Android, or both)
- Determine if native or cross-platform development is appropriate
- Assess device requirements (screen sizes, hardware capabilities)
- Identify any platform-specific features needed
2. Platform Assessment
- Evaluate iOS-specific requirements (App Store guidelines, iOS versions)
- Evaluate Android-specific requirements (Google Play Store, Android versions)
- Assess cross-platform framework suitability (React Native, Flutter, etc.)
- Identify platform-specific APIs and features needed
- Consider device fragmentation and testing requirements
3. Codebase Review
- Analyze existing mobile codebase structure
- Identify current architecture patterns used
- Review existing dependencies and third-party libraries
- Understand state management approach
- Identify any technical debt or constraints
Output Guidance
Provide:
- Clear requirements summary with platform priorities
- Platform-specific considerations and constraints
- Recommended approach (native vs cross-platform)
- Key files and patterns identified in the codebase
- Potential risks and challenges
- Device and OS version requirements
- Testing considerations
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.
- 4d ago First seen · 53 lines · 22 tokens per session scan A c56b386ff16d
mobile-mobile-analyst is an agent published in the GitHub repository MonumentalSystems/Atlas-Agent-Teams (21 stars, last pushed 27d ago), licensed MIT. It adds 22 tokens to every session and 363 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 agents, from other repositories
ux-flow-auditor
Use this agent when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app. Automatically scans SwiftUI and UIKit code for user journey defects - detects dead ends, dismiss traps, buried CTAs, missing loading/error/empty states…
swiftui-architect
Specialist in modern iOS app architecture with SwiftUI (iOS 26 / Swift 6.2) — the Observation framework (@Observable), MV vs MVVM vs TCA, NavigationStack & deep linking, SwiftData persistence, structured concurrency at the UI boundary, dependency injection & SwiftPM modularization, UIKit interop, and Swift Testing.…
android-performance-specialist
Specialist in Android app performance & diagnostics — app startup (cold/warm/hot, TTID/TTFD, App Startup lib), Baseline Profiles & Macrobenchmark, rendering/jank (frame budgets, slow/frozen frames, JankStats), ANRs (ApplicationExitInfo), memory (LeakCanary, LMK, onTrimMemory), Perfetto/Studio Profiler, Play Vitals…
mobile-ux-optimizer
Use this agent when you need to optimize UI/UX components or interfaces for mobile-first experiences, analyze existing design themes, or ensure mobile usability standards are met. Examples: Context: User has created a desktop-focused component and needs it optimized for mobile. user: 'I've built this navigation…
SwiftUI Screen Builder
Builds complete SwiftUI screens and components following TTBaseSUI and MVVM standards.
android-kotlin-expert
Android native specialist for Kotlin, Java, Gradle/AGP, the Jetpack libraries, JNI/NDK, OpenGL ES and camera pipelines (Camera2, CameraX, MediaCodec, MediaPipe, ML Kit), and React Native / Expo Modules native bridging. Use when the task touches android/ (.kt, .java, .gradle / .gradle.kts, AndroidManifest.xml…