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/narpatsinghpurohit/tstack/generating-rn-featuresnpx skills add narpatsinghpurohit/tstack --skill generating-rn-featuresgit clone --depth 1 https://github.com/narpatsinghpurohit/tstackWrote 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/narpatsinghpurohit/tstack/generating-rn-features)<a href="https://agentmods.dev/skills/narpatsinghpurohit/tstack/generating-rn-features"><img src="https://agentmods.dev/badge/skills/narpatsinghpurohit/tstack/generating-rn-features.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.00066 | $0.01308 |
| Opus 5 | $0.00033 | $0.00654 |
| Sonnet 5 | $0.00013 | $0.00262 |
| Haiku 4.5 | $0.00007 | $0.00131 |
Grade A, and why
generating-rn-features 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Live Context
- Existing features: !
ls apps/mobile/src/features/ 2>/dev/null || echo "no features yet" - Existing navigation: !
ls apps/mobile/src/navigation/ 2>/dev/null || echo "no navigation yet" - Available UI components: !
ls apps/mobile/src/components/ui/ 2>/dev/null || echo "no components — run: bunx --bun @react-native-reusables/cli@latest add <component>" - Shared schemas: !
ls packages/shared/src/schemas/ 2>/dev/null || echo "check shared/"
Task
Create feature: $ARGUMENTS
Generating React Native Features
The Pattern
Every feature uses exactly 3 files + index. No exceptions.
features/<feature-name>/
├── <name>.hook.ts # Business logic (custom hook)
├── <name>.view.tsx # Pure UI (props only, ZERO hooks)
├── <name>.tsx # Glue: calls hook, renders view
├── index.ts # Public API
├── _components/ # Private sub-components (CAN use hooks)
└── _hooks/ # Private helper hooks
UI Components — React Native Reusables
Use shadcn/ui components ported for React Native. Components live in apps/mobile/src/components/ui/.
Adding components (if not already present)
cd apps/mobile
bunx --bun @react-native-reusables/cli@latest add button input label card dialog separator avatar badge text
Key import pattern
import { Button } from "@/components/ui/button";
import { Text } from "@/components/ui/text";
import { Input } from "@/components/ui/input";
import { Card, CardContent, CardHeader, CardTitle } from "@/components/ui/card";
RN-specific component rules
- Always wrap text in
<Text>— RN does not support bare strings inside components - Button requires
<Text>child —<Button><Text>Submit</Text></Button> - Dialog/DropdownMenu/Select need PortalHost in root layout
- Label uses
nativeIDnothtmlFor—<Label nativeID="email">Email</Label> - Input uses
aria-labelledby—<Input aria-labelledby="email" />
Rules (non-negotiable)
What ships with it
3 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 · 117 lines · 66 tokens per session scan A e4d6eddeb1f2
generating-rn-features is a skill published in the GitHub repository narpatsinghpurohit/tstack (5 stars, last pushed 5mo ago), licensed MIT. It adds 66 tokens to every session and 1,308 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-31.
Other skills, from other repositories
stitch::react-native
Convert Stitch HTML designs to React Native components, or syncs/updates existing native components to align with the latest Stitch designs, using StyleSheet.
react-native-expert
Builds, optimizes, and debugs cross-platform mobile applications with React Native and Expo. Implements navigation hierarchies (tabs, stacks, drawers), configures native modules, optimizes FlatList rendering with memo and useCallback, and handles platform-specific code for iOS and Android. Use when building a React…
vercel-react-native-skills
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
expo-native-ui
Framework (OSS). Build beautiful, native-feeling Expo screens. Covers Apple HIG styling, semantic colors, native controls, SF Symbols, media, animations, visual effects, gradients, storage, and responsive layout. For routing and navigation, use the expo-router skill.
expo-web-to-native
Framework (OSS). Migrate an existing web React app to a native iOS/Android app with Expo. Use when the user wants to turn a website into a mobile app, port a Next.js/Vite/CRA React codebase to React Native, reuse web code on native incrementally, or asks how web idioms (the DOM, CSS, React Router, localStorage…
create-mobile-app
Use when the user wants to start a new Power Apps mobile app (Expo / React Native / TypeScript, targeting iOS and Android) from scratch.