Borrowing it
Nothing to install: this file belongs to chohra-med/expo_boilerplate. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/chohra-med/expo_boilerplate/development/CLAUDE.mdgit clone --depth 1 https://github.com/chohra-med/expo_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/chohra-med/expo_boilerplate/claude-md)<a href="https://agentmods.dev/instructions/chohra-med/expo_boilerplate/claude-md"><img src="https://agentmods.dev/badge/instructions/chohra-med/expo_boilerplate/claude-md/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/instructions/chohra-med/expo_boilerplate/claude-md"><img src="https://agentmods.dev/badge/instructions/chohra-med/expo_boilerplate/claude-md.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.00782 | $0.00782 |
| Opus 5 | $0.00391 | $0.00391 |
| Sonnet 5 | $0.00156 | $0.00156 |
| Haiku 4.5 | $0.00078 | $0.00078 |
Grade A, and why
expo_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 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — MobileLauncher LT
Context file for Claude Code. This acts as an entrypoint routing to our decoupled rule files.
🌿 Branches — the trunk is development, there is NO main
⛔ This repo's trunk is development. It is the GitHub default branch and the base for every PR.
⛔ main does not exist here. gh api repos/chohra-med/expo_boilerplate/branches/main returns 404. Do not
create it, do not target it, and do not assume it from habit. A PR opened against main cannot be
merged because there is nothing to merge into.
⚠️ The estate is split by family — this is where the confusion comes from:
| Family | Trunk |
|---|---|
| The AI Mobile Launcher variants (Standard · AI · openSource), Morrow Self, Mane | development |
The getwireai repos (getwireai_website, wireai-onboarding-server, wireai-activation) |
main |
So "merge to main" is correct advice for the getwireai repos and wrong for this one. Read the default branch rather than carrying a habit across families:
gh repo view --json defaultBranchRef -q .defaultBranchRef.name
⛔ A merge to development here is NOT a release. This is a React Native / Expo app: shipping to
users requires a new native build, not a merge. Never report a merged PR as shipped.
⛔ A checkout is not its trunk. Local development drifts behind origin/development routinely.
Base branches on origin/development and read trunk content with
git show origin/development:<path>, never from the working tree.
Project skill
This repo ships a Claude Code skill for code generation. To use it: /mobilelauncher <command>
Available commands: orient · feature <name> · screen <feature> <name> · component <name> · hook <name> · slice <feature> · endpoint <feature> <name> · schema <name>
See CLAUDE_SKILL.md for full documentation. Skill file: .claude/skills/mobilelauncher/skill.md
What this project is
AI-first React Native + Expo boilerplate. Feature-first architecture designed to produce consistent, predictable code with AI coding tools. Lite version of AI Mobile Launcher.
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 · 68 lines · 782 tokens per session scan A 6141b9f8dd0b
expo_boilerplate CLAUDE.md is an instructions file published in the GitHub repository chohra-med/expo_boilerplate (34 stars, last pushed 9d ago), licensed MIT. It adds 782 tokens to every session, about $0.0039 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
mcp-react-native-toolkit copilot-instructions.md
Copilot instructions for ItamiForge/mcp-react-native-toolkit, covering github copilot (vs code) instructions, project context, core rules, api validation and best practices.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).