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 richkuo/rk-skills --skill expo-app-initializegit clone --depth 1 https://github.com/richkuo/rk-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/richkuo/rk-skills/expo-app-initialize)<a href="https://agentmods.dev/skills/richkuo/rk-skills/expo-app-initialize"><img src="https://agentmods.dev/badge/skills/richkuo/rk-skills/expo-app-initialize/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/richkuo/rk-skills/expo-app-initialize"><img src="https://agentmods.dev/badge/skills/richkuo/rk-skills/expo-app-initialize.svg" alt="Reviewed on agentmods" width="80" 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.00069 | $0.01366 |
| Opus 5.5 | $0.00028 | $0.00546 |
| Sonnet 5.5 | $0.00014 | $0.00273 |
| Haiku 4.5 | $0.00007 | $0.00137 |
Grade A, and why
expo-app-initialize 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 16d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Expo App Initialize
Create a production-ready Expo React Native app from the tabs template and configure it with the standard dependencies. Use Bun for every command. Never use npm, yarn, or npx; use bunx for one-off tools.
Project name: $ARGUMENTS. If that value is empty or starts with a dollar sign (Codex does not replace the placeholder), take the name from the invocation message. If no name was passed, ask the user for a project name before running anything.
Versions
Use the latest version of every package that is compatible with the project. Never copy a version number from memory or from this skill.
- Create the project with
create-expo@latest, so the app starts on the newest stable Expo SDK. - Before any install, read the project's Expo SDK and React Native versions from
package.json. For each package that Expo does not track (react-native-mmkv,react-native-nitro-modules,expo-iap), check the latest published version, its required peer dependencies, and its documented minimum Expo SDK and React Native versions. Choose the newest version that supports the project's React Native version and architecture, and record it with every required peer dependency. If the chosen version is older than the latest, tell the user why. - Install every package with
bunx expo install <package>. It selects the version that matches the project's Expo SDK for packages Expo tracks, and the latest version for others. Install the versions and peer dependencies that the check chose in the same command. - After installation, run
bunx expo install --checkandbunx expo-doctor. Fix every version mismatch they report before prebuild.
Workflow
Run each step in order and wait for it to finish before the next. If a step fails, stop and report the exact error with troubleshooting steps. Never continue after a failed step.
- Create the project:
bunx create-expo@latest <project-name> --template tabs --yes, then work inside the new directory. - Confirm
expo-routeris already inpackage.json. The tabs template includes it. Install it withbunx expo install expo-routeronly if it is missing. - Check the packages that Expo does not track, as the Versions section describes. Record the chosen version and the required peer dependencies of each package.
- Install the dependencies:
bunx expo install react-native-mmkv react-native-nitro-modules expo-dev-client expo-iap, plus every required peer dependency that step 3 found. Write a package as<package>@<version>when step 3 chose a version older than the latest. - Run
bunx expo install --checkandbunx expo-doctor, and fix every version mismatch they report. - Run prebuild as the final setup step:
bunx expo prebuild. If the user asked for one platform only, runbunx expo prebuild --platform <android|ios>. On Windows, prebuild skips iOS with a warning; this is expected, so report it and continue. - Write the commands section into
CLAUDE.mdin the project root. Never overwrite or remove template content, and never add a second# Project Commandssection.CLAUDE.mdexists, as a file or as a symlink toAGENTS.md: append the commands section to it once.CLAUDE.mdis missing andAGENTS.mdexists: createCLAUDE.mdwith@AGENTS.mdas its first line, then the commands section. Do not changeAGENTS.md.- Neither file exists: create
CLAUDE.mdwith the commands section.
What ships with it
1 file 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.
- 16d ago First seen · 81 lines · 69 tokens per session scan A 1ea2f2cda8e9
expo-app-initialize is a skill published in the GitHub repository richkuo/rk-skills (50 stars, last pushed yesterday), licensed MIT. It adds 69 tokens to every session and 1,366 once invoked, about $0.0003 per session on Opus 5.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-10-08.
Other skills, from other repositories
android_ui_verification
Automated end-to-end UI testing and verification on an Android Emulator using ADB.
react-native
Use when building cross-platform mobile apps with React Native or Expo. Covers navigation, platform differences, list performance, native modules, offline behavior, and release builds. Trigger on "flatlist is laggy", "expo or bare react native", "bridge to a native module", "set up ota updates". Do not use for web…
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.
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.
frontend-architect
Expert frontend architecture and UI engineering for React, Next.js/App Router, TypeScript, Tailwind, shadcn/ui, accessibility, performance, design systems, Web3 transaction UX, and production-quality interfaces. Use when building components/pages, reviewing frontend code, implementing mockups, improving UX polish…
expo
Expert in Expo for React Native development. Covers Expo Router, EAS Build and Submit, development builds, native module integration, and production deployment. Knows how to build cross-platform mobile apps efficiently while maintaining access to native capabilities. Use when "expo, react native, mobile app, eas…