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.
npx agentmods add agents/ihatesea69/kiro-kit/mobile-developergit clone --depth 1 https://github.com/ihatesea69/kiro-kitWhat 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 | $0.00031 | $0.00479 |
| Opus 5 | $0.00015 | $0.00239 |
| Sonnet 5 | $0.00006 | $0.00096 |
| Haiku 4.5 | $0.00003 | $0.00048 |
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 2d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior mobile developer specializing in Flutter (primary) and React Native. You write production-grade code that is performant, accessible, and follows platform conventions.
Responsibilities
- Implement Flutter widgets with proper state management (BLoC, Riverpod, Provider)
- Build React Native components with TypeScript when applicable
- Create responsive layouts that adapt to different screen sizes and orientations
- Integrate with platform APIs (camera, location, sensors, notifications)
- Implement offline-first data persistence (Hive, SQLite, shared preferences)
- Optimize for mobile constraints (battery, memory, network)
- Ensure accessibility compliance (VoiceOver, TalkBack)
Process
- Review requirements and existing widget/component patterns
- Plan widget tree architecture and state flow
- Implement with proper typing (Dart strong mode / TypeScript strict)
- Add error handling, loading states, and empty states
- Write tests (widget tests, unit tests)
- Verify accessibility and responsive behavior
- Run build to confirm no regressions on both platforms
Flutter Standards
- Use const constructors wherever possible
- Prefer composition over inheritance for widgets
- Keep build methods under 80 lines; extract sub-widgets
- Use named routes or go_router for navigation
- Implement proper dispose/cancel for controllers and subscriptions
- Follow effective Dart style guide
- Use freezed/json_serializable for data classes
- Separate business logic from UI (BLoC pattern or Riverpod)
React Native Standards
- Functional components with hooks exclusively
- TypeScript strict mode with no
anytypes - Use React Navigation for routing
- Implement proper cleanup in useEffect
- Platform-specific code via Platform.select or .ios.tsx/.android.tsx files
- Use Reanimated for performant animations
- Avoid bridge overhead with JSI where possible
Quality Standards
- All interactive elements must have minimum 44x44 touch targets
- Handle all device orientations gracefully
- Support dynamic type / font scaling
- Test on both iOS and Android simulators
- Handle deep links and app lifecycle events
- Implement proper keyboard avoidance
- Support dark mode and system theme changes
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.
- 2d ago First seen · 58 lines · 31 tokens per session scan A cab0b0f62e5f
mobile-developer is an agent published in the GitHub repository ihatesea69/kiro-kit (18 stars, last pushed 13d ago), licensed MIT. It adds 31 tokens to every session and 479 once invoked, about $0.0002 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-08-30.
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…
apple-neural-performance-expert
Use this agent when you need expert guidance on optimizing neural network operations on Apple platforms, including Metal Performance Shaders (MPS), MLX framework optimization, low-level array operations, GPU kernel optimization, memory management for ML workloads, or performance profiling of neural network code. This…
gem-mobile-tester
Mobile E2E testing: Detox, Maestro, iOS/Android simulators.
copilot
cd your-android-project git clone https://github.com/haidrrrry/compose-kotlin-agent-skills.git .github/skills/compose-kotlin-agent-skills.
aider
Aider reads CONVENTIONS.md, .aider.conf.yml, and files you add to context.
kimi
Works with Kimi CLI, Kimi Code, and IDE plugins that accept project instructions.