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/wataru-maeda/react-native-boilerplateWrote 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/wataru-maeda/react-native-boilerplate/coding-guidelines)<a href="https://agentmods.dev/rules/wataru-maeda/react-native-boilerplate/coding-guidelines"><img src="https://agentmods.dev/badge/rules/wataru-maeda/react-native-boilerplate/coding-guidelines/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/wataru-maeda/react-native-boilerplate/coding-guidelines"><img src="https://agentmods.dev/badge/rules/wataru-maeda/react-native-boilerplate/coding-guidelines.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.01305 | $0.01305 |
| Opus 5.5 | $0.00522 | $0.00522 |
| Sonnet 5.5 | $0.00261 | $0.00261 |
| Haiku 4.5 | $0.00130 | $0.00130 |
Grade A, and why
coding-guidelines 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
React Native Expo Project - Coding Guidelines
Project Overview
React Native Expo SDK 54 project with TypeScript, Expo Router v6, Redux Toolkit, and modern development practices.
Built-in Features to Always Use
Configuration Management
- Use
utils/config.tsfor all environment variables and app configuration - Use
utils/deviceInfo.tsfor platform detection and device dimensions - Never hardcode environment values, always go through config
Theme System
- Always import from
@/themefor colors, fonts, and images - Use
@/theme/colorsinstead of hardcoded color values - Use theme system for consistent dark/light mode support
- Load assets through
@/theme/imagesand@/theme/fonts
Custom Hooks
- Use
useColorSchemefrom@/hooksfor theme detection - Use
useDataPersistfrom@/hooksfor local storage operations - Use
useKeyboardfrom@/hooksfor keyboard state management - Use
useAppSlicefrom@/slicesfor global state management
State Management
- Use Redux Toolkit slices in
@/slicesfor global state - Import from
@/slicesfor all state operations - Keep local state minimal, prefer global state for shared data
Services Layer
- Use
@/servicesfor all API calls and external integrations - Never make direct API calls from components
- Use the services layer for data transformation
Type Safety
- Use types from
@/typesfor all interfaces - Define component props interfaces for all components
- Use TypeScript strict mode - project is configured for it
Directory Structure Rules
Component Organization
components/elements- Reusable UI components (Button, Image, etc.)components/layouts- Layout-specific components (headers, navigation)scenes- Screen components (renamed from pages)app- Expo Router routes only, delegate to scenes
File Naming
- Components: PascalCase (
Button.tsx,NavigationHeader.tsx) - Hooks: camelCase with "use" prefix (
useColorScheme.ts) - Utils: camelCase (
deviceInfo.ts,config.ts) - Types: PascalCase (
User.ts,ApiResponse.ts)
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 · 198 lines · 1,305 tokens per session scan A 1b97c3f9130a
coding-guidelines is a cursor rule published in the GitHub repository wataru-maeda/react-native-boilerplate (518 stars, last pushed 1mo ago), licensed MIT. It adds 1,305 tokens to every session, about $0.0052 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
cursorrules
You are a senior Android developer. Follow these rules strictly when writing or modifying Android/Kotlin code.
kotlin
Android finance precision, RTL/i18n, and Kotlin AI skill rules.
compose-coroutines
Compose scroll/coroutine patterns — prevent programmatic scroll from being mistaken for user scroll, cancellation-safe flag resets.
android-viewmodel
Android ViewModel conventions — StateFlow, repository abstraction, coroutines, no LiveData.
typescript-coding-standards
Production TypeScript coding standards.
expo-development
React Native and Expo development guidelines, commands, and patterns.