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/madebyaris/advance-minimax-m3-cursor-rulesWrote 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/madebyaris/advance-minimax-m3-cursor-rules/mobile-cross-platform)<a href="https://agentmods.dev/rules/madebyaris/advance-minimax-m3-cursor-rules/mobile-cross-platform"><img src="https://agentmods.dev/badge/rules/madebyaris/advance-minimax-m3-cursor-rules/mobile-cross-platform/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/madebyaris/advance-minimax-m3-cursor-rules/mobile-cross-platform"><img src="https://agentmods.dev/badge/rules/madebyaris/advance-minimax-m3-cursor-rules/mobile-cross-platform.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.00000 | $0.01458 |
| Opus 5 | $0.00000 | $0.00729 |
| Sonnet 5 | $0.00000 | $0.00292 |
| Haiku 4.5 | $0.00000 | $0.00146 |
Grade A, and why
mobile-cross-platform 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 11d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cross-Platform Mobile Development
Guidance for Flutter, React Native, and Expo projects. For general coding workflow, the always-on core Code Discipline and App And Scaffold Discipline sections are canonical — especially CLI-first scaffolding and verification.
Load this rule when globs match mobile project files. Identify the stack from manifests (pubspec.yaml, package.json + native folders, app.json) before choosing patterns. Do not hand-create pubspec.yaml, Xcode/Android project trees, or .xcodeproj / .pbxproj — use the framework CLI.
Before Changing Mobile Code
- Identify stack: Flutter, React Native, Expo, or other.
- Read manifest, entry point (
main.dart,App.tsx), navigation setup, and existing state-management pattern. - Match platform folder conventions already in the repo — do not restructure unprompted.
- For new dependencies or SDK versions, verify against current official docs before recommending.
Scaffold & Verify (CLI-first)
| Stack | Create | Add deps | Typical verify |
|---|---|---|---|
| Flutter | flutter create |
flutter pub add |
flutter analyze, flutter test |
| React Native | npx react-native init |
npm install |
npx react-native doctor, build one platform |
| Expo | npx create-expo-app |
npx expo install |
npx expo doctor, npx expo start |
After structural changes, run the stack's analyze/test/build check before claiming done.
Architecture Quick Reference
Good cross-platform fit: content apps, business/productivity, MVPs, teams with web background, similar UI across platforms.
Consider more native work when: heavy AR/camera, games, deep OS integration, strict platform HIG, or performance-critical media pipelines.
| Framework | Best for | Watch out for |
|---|---|---|
| Flutter | Custom UI, performance | App size, Dart ecosystem |
| React Native | JS/TS teams, code share | Native modules, bridge overhead |
| Expo | Fast iteration, managed workflow | Native module limits (unless dev client) |
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.
- 11d ago First seen · 123 lines · 0 tokens per session scan A 93dc96236aba
mobile-cross-platform is a cursor rule published in the GitHub repository madebyaris/advance-minimax-m3-cursor-rules (125 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,458 tokens. 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 cursor rules, from other repositories
react-native
React Native: mobile app development, navigation, native modules.
native-android
Native Android (Kotlin/Java/Gradle) conventions.
react-native-js
React Native JS/TS shared layer conventions.
_project
Project-wide conventions and developer environment context (RN monorepo, no-Mac dev).
git-commit
Use this when the user asks for a git commit, commit message, or commit command.
learnship
Activate learnship agentic engineering workflows — structured phases, persistent memory, learning partner, and impeccable UI design. Use whenever a user is working on a software project or asks about project planning, phases, workflows, or how to build something.