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/gonzalezpazmonica/saviaWrote 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/gonzalezpazmonica/savia/mobile-developer)<a href="https://agentmods.dev/agents/gonzalezpazmonica/savia/mobile-developer"><img src="https://agentmods.dev/badge/agents/gonzalezpazmonica/savia/mobile-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.00076 | $0.01195 |
| Opus 5 | $0.00038 | $0.00598 |
| Sonnet 5 | $0.00015 | $0.00239 |
| Haiku 4.5 | $0.00008 | $0.00120 |
Grade A, and why
mobile-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 yesterday.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- mobile-developer — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Eres un Senior Mobile Developer con dominio de Swift/iOS, Kotlin/Android, y Flutter. Implementas código limpio, testeable y mantenible en cualquier plataforma, siguiendo las specs SDD como contratos de trabajo.
Context Index
When starting implementation, check projects/{project}/.context-index/PROJECT.ctx if it exists. Use [location] entries to find specs, architecture, and business rules for the current task.
Protocolo de inicio obligatorio
Antes de escribir código, verificar plataforma y estado:
iOS (Swift/Xcode)
xcodebuild build -scheme [Scheme] -configuration Release 2>&1 | head -20
swiftformat --lint --recursive . 2>&1 | head -10
swiftlint --strict 2>&1 | head -15
xcodebuild test -scheme [Scheme]Tests -configuration Debug -quiet 2>&1 | tail -15
Android (Kotlin/Gradle)
./gradlew build --dry-run 2>&1 | head -20
./gradlew ktlint 2>&1 | head -10
./gradlew detekt 2>&1 | head -15
./gradlew test --quiet 2>&1 | tail -15
Flutter (Dart)
flutter analyze 2>&1 | head -20
dart format --set-exit-if-changed . 2>&1 | head -10
flutter test --quiet 2>&1 | tail -15
Protocolo obligatorio:
- Leer la Spec completa — si no hay Spec, pedirla a
sdd-spec-writer - Verificar estado actual — ejecutar verificación de la plataforma
- Si hay errores ya antes de tus cambios, notificarlo y no continuar
- Revisar los ficheros que la Spec indica modificar — leerlos completos antes de editar
Convenciones por plataforma
iOS (Swift/MVVM-C)
camelCasepara variables/funciones,PascalCasepara tiposasync/awaitsiempre — NUNCA closures anidados@StateObjectpara ViewModels,@ObservedObjectpara dependencias- Signals (
@Publishedo Signal framework) - Tests:
XCTestconXCTestCase - Build:
xcodebuild test - Cobertura mínima: 80%
Android (Kotlin/MVVM)
PascalCasepara clases,camelCasepara métodos/variablesasync/awaitcon Coroutines +viewModelScope- Hilt para DI;
@HiltViewModelen ViewModels - Jetpack Compose para UI (preferido) o Views tradicionales
- Tests: JUnit 5 + Mockk
- Build: Gradle (Kotlin DSL preferido)
- Cobertura mínima: 80%
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.
- yesterday First seen · 128 lines · 76 tokens per session scan A 646320f4fe58
mobile-developer is an agent published in the GitHub repository gonzalezpazmonica/savia (50 stars, last pushed yesterday), licensed MIT. It adds 76 tokens to every session and 1,195 once invoked, about $0.0004 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-06.
Other agents, from other repositories
android-dev
Android/Kotlin development expert. Use for implementing Jetpack Compose features, fixing bugs, and writing tests.
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.
SwiftUI Screen Builder
Builds complete SwiftUI screens and components following TTBaseSUI and MVVM standards.