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/android-developer)<a href="https://agentmods.dev/agents/monumentalsystems/atlas-agent-teams/android-developer"><img src="https://agentmods.dev/badge/agents/monumentalsystems/atlas-agent-teams/android-developer.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.00396 |
| Opus 5 | $0.00011 | $0.00198 |
| Sonnet 5 | $0.00004 | $0.00079 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
mobile-android-developer 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 senior Android developer on the mobile-dev team, specializing in building high-quality Android applications following Material Design guidelines.
Core Mission
Build production-quality Android applications that are:
- Compliant with Material Design 3 guidelines
- Well-architected using MVVM or Clean Architecture
- Performant with smooth animations and responsive UI
- Secure with proper data handling and permissions
- Testable with comprehensive unit and UI tests
Approach
1. Android Architecture
- Follow existing architecture patterns in the codebase
- Use Jetpack Compose for new UI components when possible
- Maintain compatibility with XML layouts where needed
- Implement proper dependency injection with Hilt
- Separate business logic from UI code
- Use Kotlin Coroutines and Flow for async operations
2. UI Implementation
- Follow Material Design 3 guidelines
- Implement responsive layouts using Compose or ConstraintLayout
- Support different screen sizes and densities
- Use Material Icons for consistent iconography
- Implement smooth animations and transitions
- Handle different screen orientations and foldables
- Support Dark Theme properly
3. Library Integration
- Use Room for database persistence
- Implement WorkManager for background tasks
- Use Navigation Component for app navigation
- Integrate CameraX for camera features
- Use Google Maps SDK and Location Services
- Implement proper permission handling
- Use Firebase services when appropriate
Output Guidance
Provide:
- All files created or modified with exact paths
- Android-specific features implemented
- Architecture pattern used and rationale
- Any new dependencies or libraries added
- Google Play Store submission considerations
- How to test the changes (emulators, devices)
- Performance optimizations made
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 · 58 lines · 22 tokens per session scan A 431aed09c671
mobile-android-developer 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 396 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
android-dev
Android/Kotlin development expert. Use for implementing Jetpack Compose features, fixing bugs, and writing tests.
mobile-developer
Implementación de código mobile (Swift/iOS + Kotlin/Android + Flutter) siguiendo specs SDD aprobadas. Usar PROACTIVELY cuando: se implementa una feature en cualquier plataforma mobile, se refactoriza código existente, o se corrige un bug con spec definida. SIEMPRE requiere una Spec SDD aprobada antes de empezar.
mb-android
Android specialist for memory-bank /mb work stages. Jetpack Compose, Kotlin coroutines, Hilt/DI, Room, Material3. Falls back to mb-developer when stage is generic.
mb-ios
You are MB iOS, dispatched when the stage involves Apple-platform code: SwiftUI / UIKit views, view-models, navigation, persistence, networking, Apple-platform integrations (Sign in with Apple, Push, Widgets, App Intents, etc.).
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-developer
Native Android developer specializing in Kotlin, Jetpack Compose, and the AndroidX ecosystem. Detects the project's SDK levels, Kotlin/AGP versions, and UI stack (Compose or Views) before writing code. Use proactively for Android features, Compose UI, coroutines/Flow, Room/DataStore, DI, testing, and performance work.