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 instructions/wataru-maeda/react-native-boilerplate/claude-mdgit 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/instructions/wataru-maeda/react-native-boilerplate/claude-md)<a href="https://agentmods.dev/instructions/wataru-maeda/react-native-boilerplate/claude-md"><img src="https://agentmods.dev/badge/instructions/wataru-maeda/react-native-boilerplate/claude-md.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.1 | $0.01769 | $0.01769 |
| Opus 5 | $0.00885 | $0.00885 |
| Sonnet 5 | $0.00354 | $0.00354 |
| Haiku 4.5 | $0.00177 | $0.00177 |
Grade A, and why
react-native-boilerplate CLAUDE.md 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 5d 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 — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude AI Development Guide
This React Native Expo project follows specific patterns and uses built-in features for consistency and reusability.
Project Context
Technology Stack:
- React Native with Expo SDK 54
- TypeScript (strict mode)
- Expo Router v6 (flat config)
- Redux Toolkit for state management
- ESLint 9 with flat config
- React 19.1 and React Native 0.81.4
Always Use These Built-in Features
Configuration & Environment
utils/config.ts- For all environment variables and app configurationutils/deviceInfo.ts- For platform detection, screen dimensions, and device info- Never hardcode values that should come from configuration
Theme & Styling
@/theme/colors- For all color values (supports dark/light mode)@/theme/fonts- For font loading and typography@/theme/images- For image assets and loading- Always use theme system instead of hardcoded styles
Custom Hooks (Reuse These)
useColorSchemefrom@/hooks- For dark/light theme detectionuseDataPersistfrom@/hooks- For local storage operationsuseKeyboardfrom@/hooks- For keyboard state managementuseAppSlicefrom@/slices- For global state operations
State Management
- Redux Toolkit slices in
@/slices- For all global state - Use
useAppSlicefor accessing global state - Keep local state minimal, prefer global state for shared data
Services & API
@/services- For all API calls and external integrations- Never make direct API calls from components
- Use the services layer for data transformation
Type Definitions
@/types- For all TypeScript interfaces and types- Always define component prop interfaces
- Use strict TypeScript - project is configured for it
Directory Structure
app/ # Expo Router routes (keep minimal, delegate to scenes)
components/
elements/ # Reusable UI components (Button, Image, etc.)
layouts/ # Layout-specific components (headers, navigation)
scenes/ # Screen components (main UI logic)
hooks/ # Custom React hooks
slices/ # Redux Toolkit slices
services/ # API and external services
theme/ # Colors, fonts, styling system
types/ # TypeScript type definitions
utils/ # Utility functions (config, deviceInfo)
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.
- 5d ago First seen · 237 lines · 1,769 tokens per session scan A 6dd284b59e47
react-native-boilerplate CLAUDE.md is an instructions file published in the GitHub repository wataru-maeda/react-native-boilerplate (514 stars, last pushed 2d ago), licensed MIT. It adds 1,769 tokens to every session, about $0.0088 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-30.
Other instructions, from other repositories
uniwind AGENTS.md
AGENTS.md instructions for uni-stack/uniwind, covering agent instructions and checks.
expo-targets AGENTS.md
AGENTS.md instructions for csark0812/expo-targets, covering agents, product posture, sealed zones, docs ssot and safe commands.
buoy AGENTS.md
AGENTS.md instructions for Buoy-gg/buoy, covering react buoy — notes for ai agents, install, facts that models often get wrong and docs.
uniwind CLAUDE.md
Claude Code instructions for uni-stack/uniwind, a project described as: From the creators of Unistyles: The fastest Tailwind bindings for React Native.
react-native CLAUDE.md
Claude Code instructions for storybookjs/react-native, covering development commands, initial setup, development, story generation and testing.
tapflow AGENTS.md
AGENTS.md instructions for jo-duchan/tapflow, covering tapflow — agents.md (common rules), what, core value, two testing modes and why.