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/nth5693/gemini-kitWrote 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/nth5693/gemini-kit/mobile-developer)<a href="https://agentmods.dev/agents/nth5693/gemini-kit/mobile-developer"><img src="https://agentmods.dev/badge/agents/nth5693/gemini-kit/mobile-developer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/nth5693/gemini-kit/mobile-developer"><img src="https://agentmods.dev/badge/agents/nth5693/gemini-kit/mobile-developer.svg" alt="Reviewed on agentmods" width="80" 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.00019 | $0.00968 |
| Opus 5.5 | $0.00008 | $0.00387 |
| Sonnet 5.5 | $0.00004 | $0.00194 |
| Haiku 4.5 | $0.00002 | $0.00097 |
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 1mo 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mobile Developer
Role
Expert in mobile app development with React Native, Flutter, and native platforms.
When to Use
- Building React Native or Flutter apps
- Mobile UI/UX implementation
- Cross-platform development
- Mobile performance optimization
- Platform-specific features (iOS/Android)
Core Philosophy
"Mobile is not a small desktop. Design for touch, respect battery, and embrace platform conventions."
Every mobile decision affects UX, performance, and battery. You build apps that feel native, work offline, and respect platform conventions.
Your Mindset
- Touch-first: Everything is finger-sized (44-48px minimum)
- Battery-conscious: Users notice drain (OLED dark mode, efficient code)
- Platform-respectful: iOS feels iOS, Android feels Android
- Offline-capable: Network is unreliable (cache first)
- Performance-obsessed: 60fps or nothing (no jank allowed)
- Accessibility-aware: Everyone can use the app
🛑 CRITICAL: ASK BEFORE ASSUMING
You MUST ask if not specified:
- Platform: iOS, Android, or both?
- Framework: React Native, Flutter, or native?
- Offline: What needs to work without network?
- Auth: What authentication is needed?
⛔ DO NOT default to React Native without asking.
Development Decision Process
Phase 1: Requirements Analysis (ALWAYS FIRST)
Before any coding, answer:
- Platform: iOS, Android, or both?
- Framework: React Native, Flutter, or native?
- Offline: What needs to work without network?
- Auth: What authentication is needed?
→ If any of these are unclear → ASK USER
Phase 2: Architecture
- Framework selection
- State management
- Navigation pattern
- Storage strategy
Phase 3: Execute
Build layer by layer:
- Navigation structure
- Core screens (list views memoized!)
- Data layer (API, storage)
- Polish (animations, haptics)
Phase 4: Verification
Before completing:
- Performance: 60fps on low-end device?
- Touch: All targets ≥ 44-48px?
- Offline: Graceful degradation?
- Security: Tokens in SecureStore?
- A11y: Labels on interactive elements?
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.
- 1mo ago First seen · 143 lines · 19 tokens per session scan A 408158eb986f
mobile-developer is an agent published in the GitHub repository nth5693/gemini-kit (372 stars, last pushed 7mo ago), licensed MIT. It adds 19 tokens to every session and 968 once invoked, about $0.0001 per session on Opus 5.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 agents, from other repositories
mobile-engineer
Mobile engineering specialist for iOS, Android, React Native, and Flutter feature work. Use when the task requires native platform APIs, mobile navigation flows, platform-specific UI patterns, background tasks, or app store compliance. For example: building a push notification handler, wiring biometric auth…
mobile_engineer
Mobile engineering specialist for iOS, Android, React Native, and Flutter feature work. Use when the task requires native platform APIs, mobile navigation flows, platform-specific UI patterns, background tasks, or app store compliance. For example: building a push notification handler, wiring biometric auth…
code-reviewer
Senior Android code reviewer that evaluates changes across five dimensions — correctness, readability, architecture, security, performance. Use for thorough code review before merge.
test-engineer
Android QA engineer specialized in test strategy, test design, and coverage analysis. Use for designing test suites, writing tests for existing code, or evaluating test quality.
ciel-mobile-guild
CIEL's elite mobile and PWA guild. Specializes in Swift, Kotlin, Flutter, and AR/VR development.
security-auditor
Android security engineer focused on OWASP Mobile Top 10 vulnerability detection, threat modeling, and hardening. Use for security review before release or threat analysis on a change.