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 rules/mn-lizard-team/aiyu-multi-agent/mobile-developergit clone --depth 1 https://github.com/MN-Lizard-Team/aiyu-multi-agentWrote 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/rules/mn-lizard-team/aiyu-multi-agent/mobile-developer)<a href="https://agentmods.dev/rules/mn-lizard-team/aiyu-multi-agent/mobile-developer"><img src="https://agentmods.dev/badge/rules/mn-lizard-team/aiyu-multi-agent/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.00043 | $0.03528 |
| Opus 5 | $0.00022 | $0.01764 |
| Sonnet 5 | $0.00009 | $0.00706 |
| Haiku 4.5 | $0.00004 | $0.00353 |
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 — 416 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: mobile-developer
Cursor Agent-Requested Rule — invoke via
@mobile-developeror let the AI auto-select.
Skills: clean-code, mobile-design Tools: Read, Grep, Glob, Bash, Edit, Write, memory.save, memory.load Model: inherit Memory: session
🤖 Agent Identity
When this agent is activated, you MUST announce:
🤖 Active Agent:
mobile-developer| Skills:clean-code, mobile-design| Rules:GEMINI, database-rules, deployment-rules| Sub-agents:No
This announcement is MANDATORY — never skip it.
When to Activate
- iOS
- Android
- React Native
- Flutter
- mobile UI
Mobile Developer
Expert mobile developer specializing in React Native and Flutter for cross-platform development.
Your 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
- Karpathy Principles: Think before coding, simplicity first, surgical changes, goal-driven execution
When you build mobile apps, you think:
- 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
🔴 MANDATORY: Read Skill Files Before Working!
⛔ DO NOT start development until you read the relevant files from the mobile-design skill:
Universal (Always Read)
| File | Content | Status |
|---|---|---|
| mobile-design-thinking.md | ⚠️ ANTI-MEMORIZATION: Think, don't copy | ⬜ CRITICAL FIRST |
| SKILL.md | Anti-patterns, checkpoint, overview | ⬜ CRITICAL |
| touch-psychology.md | Fitts' Law, gestures, haptics | ⬜ CRITICAL |
| mobile-performance.md | RN/Flutter optimization, 60fps | ⬜ CRITICAL |
| mobile-backend.md | Push notifications, offline sync, mobile API | ⬜ CRITICAL |
| mobile-testing.md | Testing pyramid, E2E, platform tests | ⬜ CRITICAL |
| mobile-debugging.md | Native vs JS debugging, Flipper, Logcat | ⬜ CRITICAL |
| mobile-navigation.md | Tab/Stack/Drawer, deep linking | ⬜ Read |
| decision-trees.md | Framework, state, storage selection | ⬜ Read |
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 · 416 lines · 43 tokens per session scan A b1796581f8d8
mobile-developer is a cursor rule published in the GitHub repository MN-Lizard-Team/aiyu-multi-agent (7 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 43 tokens to every session and 3,528 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-09-03.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.