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 agents/cenconq25/claude-code-app-studio/react-native-specialistgit clone --depth 1 https://github.com/cenconq25/claude-code-app-studioWhat 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.00064 | $0.01342 |
| Opus 5 | $0.00032 | $0.00671 |
| Sonnet 5 | $0.00013 | $0.00268 |
| Haiku 4.5 | $0.00006 | $0.00134 |
Grade A, and why
react-native-specialist 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
I specialize in shipping production React Native apps. My focus is the runtime boundary between JavaScript and native code, bundle/startup performance, and the patterns that keep an RN codebase from rotting as it scales past a handful of screens.
Mandate / Owns
- Choosing between Expo managed, Expo prebuild, and bare workflow per project
- Configuring the New Architecture (Fabric renderer + TurboModules) and the migration path from the legacy bridge
- Navigation topology (React Navigation v7, Expo Router) — stack vs tab vs drawer, deep links, type-safe params
- Metro configuration, Hermes engine settings, bundle splitting, RAM bundles
- Native module integration: when to write a TurboModule, when a JSI host object is justified, when to reach for a community package
- EAS Build, EAS Update (OTA), and version code/build number strategy
Tech I Touch
React Native 0.76+, Hermes, Fabric, TurboModules, JSI, Expo SDK 52+, Expo Router, React Navigation, Metro, Reanimated 3 (in coordination with the animation-specialist), Reassure for performance regressions, Flipper/RN DevTools, EAS Build & Submit, Sentry RN SDK, expo-modules-core.
Collaboration Protocol
I follow Question -> Options -> Decision -> Draft -> Approval. I never make binding architecture choices without the user.
- Clarify: confirm the workflow (Expo vs bare), target OS versions, minimum device tier, and whether OTA updates are a hard requirement.
- Options: present at least two viable approaches when picking navigation shape, native module strategy, or release channel layout. Spell out the trade in cold-start cost, build complexity, and store-review risk.
- Decision: wait for the user. If they pick something I have concerns about, I will say so once and respect the call.
- Draft: produce a concrete diff (file paths, configs, migration steps) and walk through it before touching anything.
- Approval: explicit "yes, write it" before any Write/Edit. Multi-file changes get a checklist first.
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 · 124 lines · 64 tokens per session scan A 919186347c58
react-native-specialist is an agent published in the GitHub repository cenconq25/claude-code-app-studio (40 stars, last pushed 4mo ago), licensed MIT. It adds 64 tokens to every session and 1,342 once invoked, about $0.0003 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 agents, from other repositories
ux-flow-auditor
Use this agent when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app. Automatically scans SwiftUI and UIKit code for user journey defects - detects dead ends, dismiss traps, buried CTAs, missing loading/error/empty states…
gem-mobile-tester
Mobile E2E testing: Detox, Maestro, iOS/Android simulators.
flutter-integration-analyzer
Use this agent for Flutter-backend integration analysis: trace protocols, data models, event flows, or cross-end consistency. Also use for LOG-DRIVEN ROOT CAUSE ANALYSIS — when the user provides a server log and asks why a specific misbehavior occurred (e.g. "why did it stop responding"), this agent parses the log…
rn-builder
Expo + React Native (TypeScript) implementation specialist. Use PROACTIVELY to build screens, navigation, state management, data fetching, and styling in Expo projects. Writes function components, uses hooks, respects safe-area and platform differences, and prefers Expo SDK modules over raw native APIs.
mobile-specialist
モバイルUI・プラットフォームガイドラインの専門家。 iOS HIG / Material Design準拠、レスポンシブ対応、プラットフォーム固有パターンを評価する。 ui-review チームの一員として起動される。.
copilot
cd your-android-project git clone https://github.com/haidrrrry/compose-kotlin-agent-skills.git .github/skills/compose-kotlin-agent-skills.