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/ofershap/expo-best-practices/best-practicesgit clone --depth 1 https://github.com/ofershap/expo-best-practicesWrote 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/ofershap/expo-best-practices/best-practices)<a href="https://agentmods.dev/rules/ofershap/expo-best-practices/best-practices"><img src="https://agentmods.dev/badge/rules/ofershap/expo-best-practices/best-practices.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.00114 | $0.00114 |
| Opus 5 | $0.00057 | $0.00057 |
| Sonnet 5 | $0.00023 | $0.00023 |
| Haiku 4.5 | $0.00011 | $0.00011 |
Grade A, and why
best-practices 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.
What it actually says
- Use Expo Router for navigation - never set up React Navigation manually in Expo projects
- Use EAS Build for native builds - never use deprecated expo build
- Use expo-image for images - never use React Native's built-in Image component
- Use expo-secure-store for sensitive data - never use AsyncStorage for tokens or secrets
- Use Expo config plugins for native configuration - never edit native iOS/Android files directly
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 · 11 lines · 114 tokens per session scan A add805d0643f
best-practices is a cursor rule published in the GitHub repository ofershap/expo-best-practices (1 stars, last pushed 6mo ago), licensed MIT. It adds 114 tokens to every session, about $0.0006 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-31.
Other cursor rules, from other repositories
coding-guidelines
React Native Expo SDK 54 project with TypeScript, Expo Router v6, Redux Toolkit, and modern development practices.
cursor-rule
Drive the running React Native app through the rn-devtools-hub MCP server. Use when checking whether a change works in the app, tapping or typing in the UI, finding which file renders an element, proving a request succeeded, diagnosing behaviour that looks impossible, or investigating a bug after the fact.
cursorrules
React Native/Expo Mobile Development Project.
expo-development
React Native and Expo development guidelines, commands, and patterns.
best-practices
Flutter Best Practices - enforces current patterns when working with Flutter code.
app_rules
This document outlines the essential rules and guidelines for developing with the MobileLauncher LT boilerplate. Follow these rules to maintain consistency, scalability, and code quality across the project.