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/ajayyai/expo-forge/agents-mdgit clone --depth 1 https://github.com/ajayyAI/expo-forgeWrote 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/ajayyai/expo-forge/agents-md)<a href="https://agentmods.dev/instructions/ajayyai/expo-forge/agents-md"><img src="https://agentmods.dev/badge/instructions/ajayyai/expo-forge/agents-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.01259 | $0.01259 |
| Opus 5 | $0.00629 | $0.00629 |
| Sonnet 5 | $0.00252 | $0.00252 |
| Haiku 4.5 | $0.00126 | $0.00126 |
Grade A, and why
expo-forge AGENTS.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 6d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Guidance for AI coding agents (Claude Code, Cursor, Copilot, etc.) working in Expo Forge. Humans: this doubles as a conventions cheat-sheet.
Expo moves fast. Read the exact versioned docs at https://docs.expo.dev/versions/v56.0.0/ before writing native or SDK code — your training data may be stale.
Stack at a glance
- Expo SDK 56 · React 19.2 · React Native 0.85 · New Architecture · Expo Router (typed routes) · web export.
- Package manager: bun. Never use npm, yarn, pnpm, or npx. Use
bun install,bun run <script>,bunx <tool>. - Node 24 LTS (pinned in
.nvmrc);>=20.19.4is the supported floor inpackage.jsonengines. Tooling runs on Node; bun is only the package manager. - UI: Uniwind + Tailwind v4 (engine) → HeroUI Native (
@/components/ui) →@expo/ui(native primitives). Prefer existing@/components/uicomponents before reaching for raw RN. - Backend (optional): Convex + Better Auth. Off by default. Keep it cleanly removable.
- Lint/format: Biome via Ultracite. Tests: Jest + React Native Testing Library + convex-test.
- Lang: TypeScript strict. Imports use the
@/*→src/*alias.
Golden rules
- bun only. Any
npm/yarn/pnpm/npxin a command, script, or doc is wrong. - Keep auth/backend self-contained. Auth code stays under
src/features/auth/andconvex/. Route files are thin re-exports. Don't importauthClientorapi.*outside the auth feature and its existing seams (src/app/_layout.tsx, the AuthGate,src/lib). - Env-gate new integrations. A new third-party service must be a no-op when its env var is unset — the template must stay green on a fresh clone with empty
.env. Add the var toenv.ts(Zod schema) and document it in.env.example. - No secrets in git. Only
.env.exampleis tracked. Never write real keys into committed files. Server secrets live on the Convex deployment / EAS / CI. - No "AI-slop" comments. Comments explain why, not what. No
// import the thing, no narrating the obvious. Match the surrounding code's density and idiom. - No upstream-project names (the templates this derives from) anywhere except
CREDITS.md.
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.
- 6d ago First seen · 75 lines · 1,259 tokens per session scan A 33cda83ca136
expo-forge AGENTS.md is an instructions file published in the GitHub repository ajayyAI/expo-forge (23 stars, last pushed 3mo ago), licensed MIT. It adds 1,259 tokens to every session, about $0.0063 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
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.
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.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
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).