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/luizhbesper/react-native-mcp/agents-mdgit clone --depth 1 https://github.com/luizhbesper/react-native-mcpWrote 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/luizhbesper/react-native-mcp/agents-md)<a href="https://agentmods.dev/instructions/luizhbesper/react-native-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/luizhbesper/react-native-mcp/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 | $0.00729 | $0.00729 |
| Opus 5 | $0.00365 | $0.00365 |
| Sonnet 5 | $0.00146 | $0.00146 |
| Haiku 4.5 | $0.00073 | $0.00073 |
Grade A, and why
react-native-mcp 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 3d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Guidance for AI agents working on this repository (react-native-dev-mcp — an MCP server for React Native development).
Commands
pnpm install # setup (pnpm 10+, Node 22+)
pnpm test # vitest unit suites — must pass before any commit
pnpm lint # biome (format + lint); pnpm lint:fix to autofix
pnpm typecheck # tsc --noEmit
pnpm build # tsdown → dist/index.mjs
node scripts/mcp-call.mjs <tool> '<json>' # call any tool against the built server
Architecture in 30 seconds
src/tools/registry.ts—defineTool(); every tool is defined with zod in/out schemas, annotations, a spec id, and an optional capability gate. Start here.src/env/— startup capability detection; drives which tools get registered (spec 002).src/devices/—facade.tsroutes unified device ids tobackends/simctl.ts(iOS) orbackends/adb.ts(Android).src/metro/— CDP bridge to the app's Hermes runtime via Metro's/json/list: console ring buffer,evaluate_js(promise polling workaround — Hermes lacksawaitPromise), reload.src/build/— background build jobs + the YAML signature DB (signatures/*.yaml) that parses native build logs into diagnostics.
Hard rules
- Spec-first. Tool contracts live in
specs/NNN-*.md. Changing tool behavior means changing the spec in the same PR. Acceptance criteria map 1:1 to vitest case names. - stdout is the MCP transport. Never
console.loginsrc/— usesrc/shared/logger.ts(stderr, gated by--verbose). - No shell strings from inputs. All toolchain calls go through
src/shared/exec.tswith argv arrays. Foradb shell, quote withshellQuote(). - Tests must not require Xcode or the Android SDK. Mock through the exec seam with
fixtures in
test/fixtures/. Real-device suites live intest/integration/behindRUN_SIMULATOR_TESTS/RUN_ANDROID_TESTSenv vars. - Token budgets are part of every contract (spec 000): short text summary +
structuredContent; lists capped; raw logs go to disk, return the path. - Error envelope: failures the model can act on are
isError: trueresults with{code, message, remediation}— codes are registered insrc/shared/errors.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.
- 3d ago First seen · 57 lines · 729 tokens per session scan A 076fa9c930c2
react-native-mcp AGENTS.md is an instructions file published in the GitHub repository luizhbesper/react-native-mcp (2 stars, last pushed 2mo ago), licensed MIT. It adds 729 tokens to every session, about $0.0036 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.
Other instructions, from other repositories
Aix-DB CLAUDE.md
Claude Code instructions for apconw/Aix-DB, covering claude.md, plan mode, build & run commands, backend - start dev server (sanic on port 8088) and backend - install dependencies.
kiasumiles AGENTS.md
Instructions for hosanxiv/kiasumiles, covering project, architecture, commands and agent behavior.
leclap CLAUDE.md
Instructions for heristop/leclap: This repository's agent guidance lives in AGENTS.md — read it first; it is the single source of truth for structure, commands, and conventions.
skills AGENTS.md
Instructions for shikanime-labs/skills, covering skills, structure, workflow, commit style and stack (atomic delivery).
hermes-model-auto-switch AGENTS.md
Instructions for rhishi99/hermes-model-auto-switch, covering install, verify, uninstall, guardrails and conventions.
i1n-cli copilot-instructions.md
Instructions for Pakvothe/i1n-cli, covering i1n — localization as code, project setup, translation file structure, tone & voice and cli commands.