project

A project-rules add-on for an Expo mobile template. Expo is a toolkit for building mobile apps with JavaScript or TypeScript, and the rules describe this template’s stack, file conventions, design tokens, checks, and agent roles.

In plain words
What is it for?
Use it before editing the project to load the handoff notes and follow the template’s conventions and verification commands.
Why use it?
It gives coding tools a shared reference for how the repository is organized and how changes should be made.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/kitariel/expo-mobile-template/project
Clone the repo
git clone --depth 1 https://github.com/kitariel/expo-mobile-template

Made for: Cursor.

Per session 160 This file is loaded in full into every session.
When invoked 160 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00160 $0.00160
Opus 5 $0.00080 $0.00080
Sonnet 5 $0.00032 $0.00032
Haiku 4.5 $0.00016 $0.00016

Measured 2d ago against content hash 8dc0d9573fdc, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

project 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 2d 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.

.cursor/rules/project.mdc · 16 lines

What it actually says

Before your first edit, read docs/HANDOFF.md. It describes where the project stands right now, including anything left half-finished by whichever AI tool worked on it last. Update it at checkpoints as you work — this repo is passed between Claude Code, Codex, and Cursor, and that file is the baton.

All other project instructions live in AGENTS.md at the repository root: the stack (Expo SDK 57 / expo-router / TypeScript strict), directory conventions, the design-token rule, verification commands, and the agent roster.

Do not duplicate their content here. AGENTS.md is the single source of truth.

Changes

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.

  1. 2d ago First seen · 16 lines · 160 tokens per session scan A 8dc0d9573fdc

Subscribe to this mod's changes

project is a cursor rule published in the GitHub repository kitariel/expo-mobile-template (6 stars, last pushed 11d ago), licensed MIT. It adds 160 tokens to every session, about $0.0008 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.