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/nedcodes-ok/cursorrules-collectionWrote 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/nedcodes-ok/cursorrules-collection/expo)<a href="https://agentmods.dev/rules/nedcodes-ok/cursorrules-collection/expo"><img src="https://agentmods.dev/badge/rules/nedcodes-ok/cursorrules-collection/expo/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/nedcodes-ok/cursorrules-collection/expo"><img src="https://agentmods.dev/badge/rules/nedcodes-ok/cursorrules-collection/expo.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.00494 | $0.00494 |
| Opus 5.5 | $0.00198 | $0.00198 |
| Sonnet 5.5 | $0.00099 | $0.00099 |
| Haiku 4.5 | $0.00049 | $0.00049 |
Grade A, and why
expo 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 1mo 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Expo Cursor Rules
You are an expert Expo/React Native developer. Follow these rules:
Project Structure
- Use Expo Router for file-based navigation. Routes in app/ directory
- Shared components in components/, hooks in hooks/, utils in utils/
- Platform-specific files: Component.ios.tsx, Component.android.tsx, Component.web.tsx
- Use expo-constants for app config. Access via Constants.expoConfig
Navigation (Expo Router)
- File-based routing: app/(tabs)/index.tsx, app/[id].tsx, app/_layout.tsx
- Use Stack, Tabs, Drawer from expo-router for layout types
- Type-safe navigation with useRouter() and Link component
- Deep linking configured via app.json scheme field
- Use useLocalSearchParams() for route params, typed with generics
Components & Styling
- StyleSheet.create() for all styles — never inline style objects
- Use Pressable over TouchableOpacity. Better accessibility and customization
- Platform.select() for platform-specific values, not runtime if/else
- SafeAreaView (from react-native-safe-area-context) on all screen components
- FlatList for lists, never ScrollView with .map() — virtualization matters
State & Data
- TanStack Query for server state. AsyncStorage for local persistence
- Zustand or Jotai for global client state — avoid Redux in Expo projects
- Use expo-secure-store for sensitive data (tokens, credentials), not AsyncStorage
- Handle offline state: check NetInfo, queue mutations, sync on reconnect
Native Features
- Use Expo SDK modules first (expo-camera, expo-location, expo-notifications)
- Request permissions with expo-* permission hooks. Handle denied state in UI
- Use expo-image over React Native Image — better caching and performance
- Animations: react-native-reanimated for complex, Animated API for simple
Build & Config
- EAS Build for production builds. Never eject unless absolutely required
- app.json/app.config.ts for all Expo config. Use config plugins for native customization
- Environment variables via .env with expo-constants, not process.env
- OTA updates with expo-updates. Set fallbackToCacheTimeout for reliability
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.
- 1mo ago First seen · 48 lines · 494 tokens per session scan A b81a48128eb9
expo is a cursor rule published in the GitHub repository nedcodes-ok/cursorrules-collection (38 stars, last pushed 7mo ago), licensed MIT. It adds 494 tokens to every session, about $0.0020 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-30.
Other cursor rules, from other repositories
03-ui
UI, layout, theming and localization standards.
01-tech-stack
Android tech stack and project standards.
09-android-best-practices
Android engineering best practices.
04-kotlin
Cursor rule "04-kotlin" from orbitalsonic/AndroidPilot, covering kotlin rules, prefer, coroutines, null safety and naming.
06-error-handling
Cursor rule "06-error-handling" from orbitalsonic/AndroidPilot, covering error handling, never, always, coroutines and validation.
05-performance
Android performance rules.