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/salah-xd/appcn/claude-mdgit clone --depth 1 https://github.com/Salah-XD/appCNWrote 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/salah-xd/appcn/claude-md)<a href="https://agentmods.dev/instructions/salah-xd/appcn/claude-md"><img src="https://agentmods.dev/badge/instructions/salah-xd/appcn/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.02524 | $0.02524 |
| Opus 5 | $0.01262 | $0.01262 |
| Sonnet 5 | $0.00505 | $0.00505 |
| Haiku 4.5 | $0.00252 | $0.00252 |
Grade A, and why
appCN 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
appCN
A shadcn-philosophy component system for React Native / Expo: copy-paste ownership, editable
source, NativeWind styling, motion-first premium defaults. Distributed through the shadcn CLI's
custom-registry mechanism (npx shadcn add <url>), not as a black-box npm package.
Positioning
- Base: a broad mobile component library (button, sheet, input, list, tabs, …).
- Featured / hero: an AI-native mobile collection (
packages/ui/src/ai/*) — streaming chat bubble, voice waveform, typing/thinking states, copilot overlay. This is the marketed wedge that differentiates appCN from the incumbent (React Native Reusables). - Differentiator: the previews experience — every component is viewable interactively in the
browser, live on a real phone via QR (Expo), and as video.
- The interactive web preview is an iframe into the Expo web build (
expo start --web, default:8081, route/c/<slug>), NOT react-native-web inside Next. Same code path as the phone, so web and device previews are guaranteed identical and we avoid NativeWind-in-Next config hell. - The web app therefore has no React Native / NativeWind deps — it's plain Next.js + Tailwind v3.
- The interactive web preview is an iframe into the Expo web build (
Monorepo map
Turborepo + pnpm workspaces. The cross-bundler boundary (Metro for Expo vs Next for web) is handled inside the repo, not by splitting repos.
apps/
web/ Next.js App Router — landing + docs + interactive previews + the registry JSON it serves
showcase/ Expo Router app — renders every component; the target the docs QR codes deep-link into
packages/
ui/ ★ SINGLE SOURCE OF TRUTH for all components (RN + NativeWind). Also exports the
shared Tailwind/NativeWind preset + theme tokens consumed by BOTH apps.
cli/ @app-cn/cli — the `appcn` binary: RN-aware shadcn wrapper (init + add). tsup-bundled.
tsconfig/ shared TypeScript bases (@app-cn/tsconfig)
Golden rule: component source lives ONLY in packages/ui/src. The Expo app, the web previews,
and the registry builder all read from there. Never fork a component into an app.
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 · 169 lines · 2,524 tokens per session scan A 741525c0aced
appCN CLAUDE.md is an instructions file published in the GitHub repository Salah-XD/appCN (3 stars, last pushed 3mo ago), licensed MIT. It adds 2,524 tokens to every session, about $0.0126 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
coss AGENTS.md
AGENTS.md instructions for cosscom/coss, covering agents.md and main documentation.
tamagui CLAUDE.md
Claude Code instructions for tamagui/tamagui, a project described as: Style React fast with 100% parity on React Native, an optional UI kit, and optimizing compiler.
ui CLAUDE.md
Claude Code instructions for persianlabs/ui, covering claude.md, what this is, commands, before pushing and architecture: components exist in two places, on purpose.
ui AGENTS.md
AGENTS.md instructions for persianlabs/ui, covering this is not the next.js you know, adding a new component or utility, component and utility previews, copyable page and .md endpoint and guard script.
MobiAI-Core CLAUDE.md
Claude Code instructions for ArisGuimera/MobiAI-Core, covering mobiai — mobile development ai ecosystem, bootstrap and principles.
freetube CLAUDE.md
Instructions for leshkodev/freetube, covering claude.md, 1. what this project is, 2. non-negotiable constraints, 3. tech stack (locked) and 4. project structure.