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 skills add johnku2011/boilerplates-with-ai-skills --skill react-native-developmentgit clone --depth 1 https://github.com/johnku2011/boilerplates-with-ai-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/johnku2011/boilerplates-with-ai-skills/react-native-development)<a href="https://agentmods.dev/skills/johnku2011/boilerplates-with-ai-skills/react-native-development"><img src="https://agentmods.dev/badge/skills/johnku2011/boilerplates-with-ai-skills/react-native-development/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/johnku2011/boilerplates-with-ai-skills/react-native-development"><img src="https://agentmods.dev/badge/skills/johnku2011/boilerplates-with-ai-skills/react-native-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00034 | $0.00510 |
| Opus 5 | $0.00017 | $0.00255 |
| Sonnet 5 | $0.00007 | $0.00102 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
react-native-development 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 9d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
React Native Development (Expo)
Overview
Build mobile UI with Expo and React Native. Keep screens in components; extract
testable logic into pure functions under src/.
Process
- Prefer React Native core components and
StyleSheet.createbefore adding UI libraries. - Keep
App.tsx(or future screens) focused on layout and wiring; move non-trivial logic to pure helpers you can test withnpm test. - Handle platform differences explicitly (
Platform.OS, platform-specific files) instead of guessing runtime behavior. - Respect safe areas and accessibility: meaningful labels, tappable targets, sufficient contrast.
- Verify with
npm run typecheckandnpm testbefore claiming completion.
Structure
- Screens under
app/orsrc/screens/(follow existing project layout). - Shared UI in small components; no mega-files.
- Navigation: use Expo Router conventions if added later; document stack changes.
Testing Strategy
- Unit tests for pure functions (formatting, validation, reducers) — required.
- Component tests when logic is intertwined with rendering — optional in this starter; prefer extracting logic first.
- Device/simulator for layout, gestures, and platform-specific UI — manual smoke test before release.
Guidelines
- Do not block the JS thread with heavy sync work; defer or chunk large tasks.
- Read secrets from environment at build time via Expo config — never hardcode API keys in source.
- Adding native modules may require an Expo config plugin and a dev client build; document that before adding dependencies.
- Test on at least one target (iOS simulator, Android emulator, or web) for UI
changes; logic-only changes can rely on
npm test. - Use
project-securitychecks for auth tokens, deep links, and WebViews.
Anti-patterns
- Copy-pasting web React patterns that assume DOM APIs.
- Storing refresh tokens in AsyncStorage without encryption requirements documented.
- Skipping tests because "it's just UI" while logic lives in the component.
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.
- 9d ago First seen · 60 lines · 34 tokens per session scan A 384107428604
react-native-development is a skill published in the GitHub repository johnku2011/boilerplates-with-ai-skills (240 stars, last pushed 15d ago), licensed MIT. It adds 34 tokens to every session and 510 once invoked, about $0.0002 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 skills, from other repositories
animate-expo
Build animations in React Native and Expo, making the decisions in the order that determines whether they feel right — should it animate, which thread it runs on, which properties, spring or timing, how the gesture hands off, how it degrades. Writes the implementation with Reanimated, Gesture Handler, Expo Router and…
leanback-to-compose-tv-migration
Provides instructions and architectural patterns for migrating Android TV applications from legacy Leanback UI Toolkit, Android Views, or Support Fragments to Jetpack Compose for TV (androidx.tv). Use this skill for Leanback to Compose migrations, including browse screen, settings screen, authentication screen, login…
maui-data-binding
Guidance for .NET MAUI XAML and C# data bindings — compiled bindings, INotifyPropertyChanged / ObservableObject, value converters, binding modes, multi-binding, relative bindings, fallbacks, and MVVM best practices. USE FOR: setting up compiled bindings with x:DataType, implementing INotifyPropertyChanged or…
web-haptics
Add haptic feedback to web apps using the web-haptics library. Use when building mobile-facing UIs that need tactile feedback on buttons, toggles, forms, pickers, and other interactive elements.
migrate-xml-views-to-jetpack-compose
Provides a structured workflow for migrating an Android XML View to Jetpack Compose. This skill details the step-by-step process, from planning and dependency setup, to theming and layout migration, validation and XML cleanup. Use this skill when you need to migrate an XML View to Jetpack Compose in an Android…
axiom-swiftui
Use when building, fixing, or improving ANY SwiftUI UI — views, navigation, layout, animations, performance, architecture, gestures, debugging, iOS 26 features.