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 fatihkan/badi --skill expo-prebuildgit clone --depth 1 https://github.com/fatihkan/badiWrote 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/fatihkan/badi/expo-prebuild)<a href="https://agentmods.dev/skills/fatihkan/badi/expo-prebuild"><img src="https://agentmods.dev/badge/skills/fatihkan/badi/expo-prebuild/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/fatihkan/badi/expo-prebuild"><img src="https://agentmods.dev/badge/skills/fatihkan/badi/expo-prebuild.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.00075 | $0.01519 |
| Opus 5 | $0.00037 | $0.00759 |
| Sonnet 5 | $0.00015 | $0.00304 |
| Haiku 4.5 | $0.00007 | $0.00152 |
Grade C, and why
expo-prebuild scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf node_modules .expo ios android How it starts
The opening of the file, as written. The whole thing — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
expo-prebuild
A guide to the managed → bare transition and continuous native sync with npx expo prebuild. Managing the ios/ and android/ directories, .easignore, the native-upgrade flow, and custom-mod application order. Plugin writing lives in expo-config-plugin.
What It Does
- Generates the native projects with the
prebuildcommand - Continuous native generation (CNG) vs persisted native decision
- EAS build cleanup with
.easignore - Native upgrade flow (Expo SDK + dependencies)
- Prebuild cache and
--cleanflag usage - Custom mod compose order
Prebuild Commands
# Basic
npx expo prebuild
# Single platform
npx expo prebuild --platform ios
npx expo prebuild --platform android
# Clean start (delete and regenerate the native directories)
npx expo prebuild --clean
# Specific template
npx expo prebuild --template <github-url-or-tarball>
# Skip dependency install
npx expo prebuild --no-install
Two Strategies
A) Continuous Native Generation (CNG) — Recommended
- Don't commit the
ios/andandroid/directories prebuildruns before every build (EAS does it automatically)- Native config is fully generated from
app.config.ts+ plugins - Advantage: easy SDK upgrades, no conflicts
- Limit: very custom native changes = you must write a config plugin
B) Persisted Native (the old "bare")
ios/andandroid/are committed- Don't run
prebuild— go straight to Xcode/Android Studio - Advantage: full native control
- Limit: manual SDK upgrades, expect conflicts
.gitignore (for CNG)
/ios
/android
.easignore (speeds up the EAS build)
/ios
/android
.expo/
node_modules/
*.test.ts
__tests__/
docs/
apps/web/
packages/web-only/
Every file in
.gitignoreis fine for.easignoretoo. Without.easignore, EAS uses.gitignore.
Native Upgrade Flow
# 1. Upgrade the Expo SDK
npx expo install expo@latest
npx expo install --check # detect incompatible packages
npx expo install --fix # auto-pull compatible versions
# 2. Prebuild again (always, if using CNG)
npx expo prebuild --clean
# 3. Pod install (iOS)
cd ios && pod install && cd ..
# 4. Test
npx expo run:ios
npx expo run:android
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 · 219 lines · 75 tokens per session scan C ccd209052a87
expo-prebuild is a skill published in the GitHub repository fatihkan/badi (7 stars, last pushed 3d ago), licensed MIT. It adds 75 tokens to every session and 1,519 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-06.
Other skills, from other repositories
web-artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
landing-page-generator
Generate complete, deploy-ready landing pages from any repository. Use when creating a homepage for an open-source project, building a project website, converting a README into a marketing page, or standardizing landing pages across multiple repos.
heroui
Build accessible UIs using HeroUI v3 components (React + Tailwind CSS v4 + React Aria). Use when creating React interfaces, selecting UI components, implementing forms, navigation, overlays, or data display. Use when installing HeroUI v3, customizing themes, accessing component documentation, building with compound…
mobile-development
Build modern mobile applications with React Native, Flutter, Swift/SwiftUI, and Kotlin/Jetpack Compose. Covers mobile-first design principles, performance optimization (battery, memory, network), offline-first architecture, platform-specific guidelines (iOS HIG, Material Design), testing strategies, security best…
coding-standards
Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development.
frontend-patterns
Frontend development patterns for React, Next.js, state management, performance optimization, and UI best practices.