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 skills/aarvion-ai/stackwise-skills/react-native-expertnpx skills add Aarvion-AI/stackwise-skills --skill react-native-expertgit clone --depth 1 https://github.com/Aarvion-AI/stackwise-skillsWrote 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/skills/aarvion-ai/stackwise-skills/react-native-expert)<a href="https://agentmods.dev/skills/aarvion-ai/stackwise-skills/react-native-expert"><img src="https://agentmods.dev/badge/skills/aarvion-ai/stackwise-skills/react-native-expert.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.00127 | $0.02087 |
| Opus 5 | $0.00063 | $0.01043 |
| Sonnet 5 | $0.00025 | $0.00417 |
| Haiku 4.5 | $0.00013 | $0.00209 |
Grade A, and why
react-native-expert 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 4d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
React Native Expert
Turns Claude into a senior React Native engineer who ships Expo-managed, New Architecture apps with TypeScript, tested navigation, 60fps lists, and a working EAS release pipeline.
When to Use This Skill
- Building screens, layouts, tabs, or modals with Expo Router file-based navigation
- Deciding between Expo managed workflow, prebuild (CNG), and bare React Native
- Migrating to or debugging the New Architecture (Fabric renderer, TurboModules, bridgeless mode)
- Fixing dropped frames in long lists (FlashList) or animations (Reanimated 3 worklets)
- Writing platform-specific code (iOS/Android/web) without forking the whole component tree
- Authoring native modules with the Expo Modules API (Swift/Kotlin) or consuming third-party ones
- Setting up EAS Build, EAS Update, and a Jest + React Native Testing Library + Maestro test stack
Core Workflow
- Analyze - read
package.json(RN and Expo SDK versions,newArchEnabledis default-on in 0.76+),app.json/app.config.ts(plugins, scheme, runtimeVersion), and theapp/directory to learn the route tree. Check foreas.json,metro.config.js, and an existing test setup before writing anything. Note whether the project is managed, prebuild, or bare - it changes what you are allowed to touch (ios//android/are generated artifacts under prebuild). - Implement - write TypeScript throughout. Use Expo Router conventions (
_layout.tsx,[param].tsx,(group)/) for navigation, typed routes viaexperiments.typedRoutes. Every interactive element getsaccessibilityLabel/accessibilityRoleand a stabletestID- this is what makes the app automatable by Maestro and QA tooling, not optional polish. - Verify types and lint - run
npx tsc --noEmitandnpx expo lint; fix all reported issues and re-run until clean before proceeding. - Verify Expo project health - run
npx expo-doctorafter any dependency, config-plugin, orapp.jsonchange; fix all reported issues (usually withnpx expo install --fix) and re-run until clean. - Test - run
npx jest; write or update Jest + React Native Testing Library tests for the change (query by role/label/testID, never by implementation detail). If any test fails, fix the code or the test and re-run until all pass. For flows that cross screens, add or update a Maestro flow in.maestro/and runmaestro test .maestro/until it passes. - Prove it works on a device - run
npx expo startand exercise the change in a simulator/emulator or dev build (npx expo run:ios/run:androidwhen native code changed). Confirm the actual behavior - navigation lands on the right screen, lists scroll at 60fps with the perf monitor open, both platforms if the change is platform-sensitive. If it misbehaves, fix and re-verify from step 3 until the observed behavior is correct.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 123 lines · 127 tokens per session scan A 2b1f9bd20b8d
react-native-expert is a skill published in the GitHub repository Aarvion-AI/stackwise-skills (5 stars, last pushed yesterday), licensed MIT. It adds 127 tokens to every session and 2,087 once invoked, about $0.0006 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 skills, from other repositories
add-sample-data
Use when the user wants to seed Dataverse tables with realistic sample records so a freshly-scaffolded code app shows real-looking data on first launch. Generates contextually appropriate rows from each table's schema and inserts them in dependency order. Mirrors…
add-native
Public entry point for native device capabilities and native controls — camera, image picker, barcode/QR scanner, document picker, file picker, secure storage, file system, sharing, PDF generation/viewing, pen/signature capture, background GPS/geolocation tracking, or supported local file workflows — in a Power Apps…
add-pdf-report
Internal implementation skill invoked by /add-native for app-generated PDF report workflows using expo-print and, when present, expo-sharing.
enable-tables-offline
Internal mobile-app workflow read and executed only by /setup-offline-profile to enable Dataverse table prerequisites for a Mobile Offline Profile.
preview-screens
Use when the user wants to preview generated screens in a browser without starting Metro / a simulator — for example after /create-mobile-app finishes or after /edit-app regenerates a screen.
add-geolocation
Internal implementation skill invoked by /add-native for native background GPS tracking with durable storage and Dataverse sync using @microsoft/power-apps-native-bglocation.