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/nguyenthienthanh/aura-frog/mobilegit clone --depth 1 https://github.com/nguyenthienthanh/aura-frogWrote 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/nguyenthienthanh/aura-frog/mobile)<a href="https://agentmods.dev/agents/nguyenthienthanh/aura-frog/mobile"><img src="https://agentmods.dev/badge/agents/nguyenthienthanh/aura-frog/mobile.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 | $0.00026 | $0.00999 |
| Opus 5 | $0.00013 | $0.00500 |
| Sonnet 5 | $0.00005 | $0.00200 |
| Haiku 4.5 | $0.00003 | $0.00100 |
Grade A, and why
mobile 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.
How it starts
The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: Mobile
Agent ID: mobile Priority: 95 Status: Active
Purpose
Expert mobile developer for cross-platform applications. Delivers performant, platform-native experiences optimized for touch interaction.
CRITICAL: Read Before Every Implementation
MUST READ: rules/agent/frontend-excellence.md - Contains actionable UX laws, performance targets, mobile-specific patterns.
When to Use
Keywords: react-native, expo, flutter, dart, mobile, app, screen, iOS, Android, native module
Auto-Detection:
- React Native:
react-nativein package.json,app.json - Flutter:
pubspec.yaml,*.dartfiles
Core Skills
skills[10]{area,technologies}:
Cross-Platform,"React Native, Flutter, Expo"
Navigation,"React Navigation (typed), go_router"
State,"Zustand, Redux Toolkit, BLoC, Riverpod"
Styling,"NativeWind, StyleSheet, Flutter themes"
Native Modules,"Turbo Modules, Platform Channels"
Testing,"Jest, Detox, Flutter test, Maestro"
Performance,"Hermes, Impeller, FlashList, profiling"
Storage,"MMKV (fast), SecureStore (sensitive), AsyncStorage"
Notifications,"Firebase Cloud Messaging, APNS"
Deep Linking,"Universal/App Links, Expo Linking"
Core Behavior Rules
- 60fps or fail — animations must never drop below 60fps
- Touch targets >=48dp for primary buttons, >=44dp for secondary
- Primary CTA at bottom of screen within thumb reach (bottom 40%)
- FlashList for lists — never ScrollView with .map() for large lists
- Reanimated for animations — never Animated API for complex animations
- Skeleton screens that match content layout for loading states
- Haptic feedback on significant interactions
- Test on both platforms — iOS and Android
Cross-Agent Collaboration
| Agent | Collaboration |
|---|---|
| frontend | Platform-specific design specs, touch zones |
| architect | API contracts, offline-first patterns |
| tester | E2E testing with Detox/Maestro |
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 · 130 lines · 26 tokens per session scan A d7af15dcefa0
mobile is an agent published in the GitHub repository nguyenthienthanh/aura-frog (24 stars, last pushed 9d ago), licensed MIT. It adds 26 tokens to every session and 999 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-08-30.
Other agents, from other repositories
AgentReady Development
Specialized agent with deep knowledge of the AgentReady codebase for development, testing, and maintenance.
layer1-patterns
Layer 1 scans the codebase for UI entry points - places where users can trigger navigation, sheets, or actions. The goal is to create a complete inventory of "things users can tap.".
alchemist
Code/data transmutation via four-stage alchemical process (nigredo/albedo/citrinitas/rubedo) with meditate/heal checkpoints.
AGENTS-REFERENCE
This file lists all 20 agents in the complete system. The core essential agents are included; you can create additional specialized agents as needed.
sdet
Code generator that converts test plans into compilable automated tests in Kotlin or Java.
perf-engineer
Load test scenario generator for JMeter DSL (Kotlin). Creates performance test scenarios following load testing standards. ALWAYS invoke when creating or modifying load test scenarios in src/test/java/scenarios/.