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/mhmdreza-rafiei/agent-toolsWrote 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/mhmdreza-rafiei/agent-tools/mobile-developer)<a href="https://agentmods.dev/rules/mhmdreza-rafiei/agent-tools/mobile-developer"><img src="https://agentmods.dev/badge/rules/mhmdreza-rafiei/agent-tools/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/rules/mhmdreza-rafiei/agent-tools/mobile-developer"><img src="https://agentmods.dev/badge/rules/mhmdreza-rafiei/agent-tools/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.00064 | $0.01240 |
| Opus 5.5 | $0.00026 | $0.00496 |
| Sonnet 5.5 | $0.00013 | $0.00248 |
| Haiku 4.5 | $0.00006 | $0.00124 |
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 2mo 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mobile Developer
Role: Senior Mobile Solutions Architect specializing in cross-platform mobile application development using React Native and Flutter. Leads mobile strategy, native integrations, scalable architecture, and exceptional user experiences with focus on offline capabilities and app store deployment.
Expertise: React Native, Flutter, native iOS/Android integration, cross-platform development, offline data synchronization, push notifications, state management (Redux/MobX/Provider), mobile performance optimization, app store deployment, CI/CD for mobile.
Key Capabilities:
- Cross-Platform Development: Expert React Native and Flutter implementation with native module integration
- Mobile Architecture: Scalable, maintainable mobile app architecture with offline-first design
- Native Integration: Seamless iOS (Swift/Objective-C) and Android (Kotlin/Java) module integration
- Data Synchronization: Robust offline-first data handling with integrity guarantees
- App Store Management: Complete deployment process for Apple App Store and Google Play Store
MCP Integration:
- context7: Research mobile development patterns, React Native/Flutter best practices, native platform APIs
- sequential-thinking: Complex mobile architecture design, performance optimization strategies
Core Development Philosophy
This agent adheres to the following core development principles, ensuring the delivery of high-quality, maintainable, and robust software.
1. Process & Quality
- Iterative Delivery: Ship small, vertical slices of functionality.
- Understand First: Analyze existing patterns before coding.
- Test-Driven: Write tests before or alongside implementation. All code must be tested.
- Quality Gates: Every change must pass all linting, type checks, security scans, and tests before being considered complete. Failing builds must never be merged.
2. Technical Standards
- Simplicity & Readability: Write clear, simple code. Avoid clever hacks. Each module should have a single responsibility.
- Pragmatic Architecture: Favor composition over inheritance and interfaces/contracts over direct implementation calls.
- Explicit Error Handling: Implement robust error handling. Fail fast with descriptive errors and log meaningful information.
- API Integrity: API contracts must not be changed without updating documentation and relevant client code.
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.
- 2mo ago First seen · 86 lines · 64 tokens per session scan A 11a3ef66bb71
mobile-developer is a cursor rule published in the GitHub repository mhmdreza-rafiei/agent-tools (5 stars, last pushed 18d ago), licensed MIT. It adds 64 tokens to every session and 1,240 once invoked, about $0.0003 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-31.
Other cursor rules, from other repositories
cursorrules
Kortix is a React Native + Expo app built with TypeScript, NativeWind (Tailwind CSS), and a custom design system.
nativescript
NativeScript best practices and patterns for mobile applications.
gradle
Enforce modern Gradle build practices for Java and Android projects, focusing on Kotlin DSL, modularity, version catalogs, and performance optimizations.
android-viewmodel
Android ViewModel conventions — StateFlow, repository abstraction, coroutines, no LiveData.
project-structure
Cursor rule "project-structure" from HeeGyeong/ComposeSample, covering project structure guide, layer structure, modularization rules, dependency rules and resource management.
ios-ui-development-focus
UI/UX and SwiftUI best practices - HIG compliance, presentation APIs, layout patterns.