agentmods.dev

expo-prebuild

expo-prebuild is a skill for Claude Code from fatihkan/badi. It costs 75 tokens per session (1,519 once invoked), scanned C, original, MIT.

A guide to using Expo prebuild to generate and maintain the native iOS and Android project folders for a React Native app. It covers the transition from Expo's managed setup to direct native project work.

In plain words
What is it for?
Use it to generate one or both native projects, choose whether to keep those folders in version control, apply custom configuration, and upgrade Expo SDK native code.
Why use it?
It helps keep generated native projects in sync with Expo settings and dependencies instead of making uncontrolled manual changes. It also explains clean regeneration and native upgrade work.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions Claude Code.

Part of the badi plugin — 81 skills, 86 commands, 30 agents, 7 hooks shipped together

not rated 7repo 23d ago C scan 75 tokens original MIT

Good fit Use it to generate one or both native projects, choose whether to keep those folders in version control, apply custom configuration, and upgrade Expo SDK native code.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/fatihkan/badi/expo-prebuild
View source ↗ fatihkan/badi npmjs.com
Install

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.

Any agent
npx skills add fatihkan/badi --skill expo-prebuild
Clone the repo
git clone --depth 1 https://github.com/fatihkan/badi

Made for: Claude Code.

Or install badi, the plugin that ships this one along with the rest of its 81 skills, 86 commands, 30 agents, 7 hooks.

Wrote 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.

agentmods badge for expo-prebuild

README.md
[![agentmods](https://agentmods.dev/badge/skills/fatihkan/badi/expo-prebuild/github.svg)](https://agentmods.dev/skills/fatihkan/badi/expo-prebuild)
Your own site
<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.

agentmods 80×15 button for expo-prebuild

Your own site · 80×15
<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>
Per session 75 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,519 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00075 $0.01519
Opus 5.5 $0.00030 $0.00608
Sonnet 5.5 $0.00015 $0.00304
Haiku 4.5 $0.00007 $0.00152

Measured 1mo ago against content hash ccd209052a87, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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
.claude/skills-vault/expo-prebuild/SKILL.md · 219 lines

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 prebuild command
  • Continuous native generation (CNG) vs persisted native decision
  • EAS build cleanup with .easignore
  • Native upgrade flow (Expo SDK + dependencies)
  • Prebuild cache and --clean flag 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/ and android/ directories
  • prebuild runs 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/ and android/ 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 .gitignore is fine for .easignore too. 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

Read the full file on GitHub · 219 lines

Changes

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.

  1. 1mo ago First seen · 219 lines · 75 tokens per session scan C ccd209052a87

Subscribe to this mod's changes

expo-prebuild is a skill published in the GitHub repository fatihkan/badi (7 stars, last pushed 23d ago), licensed MIT. It adds 75 tokens to every session and 1,519 once invoked, about $0.0003 per session on Opus 5.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.

Claude CodeFrontendMobileReactagentsai-workflowclideveloper-toolshooks
Related

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.

AvinashP/AgentsAtlas · 64 tokens

react

Use when building or reviewing a client-side React SPA bundled by Vite (React 19.2): components, where state lives, hooks, server data fetching, client routing, re-render and effect bugs. NOT App Router / server components / SSR (that is nextjs); NOT native screens (that is react-native).

ericrisco/rsc-harness · 70 tokens

capacitor-react

Guides the agent through Capacitor app development with React — project structure, hooks for native features, state management patterns, using Capacitor plugins in React components, and React-specific best practices. Do not use for Ionic Framework with React (use ionic-react), migrating or upgrading Capacitor apps or…

capawesome-team/skills · 70 tokens

state-management

State Management - React Query, Zustand, MMKV. Use when managing application state.

TheBeardedBearSAS/claude-craft · 20 tokens

rn-best-practices

This skill should be used when writing or reviewing React Native / Expo code — before writing list rendering, animations, data fetching, component APIs, navigation, or image/media UI — and when asked to "review best practices", "check performance", "optimize renders", "review list rendering", "check animation…

Lykhoyda/rn-dev-agent · 98 tokens

pr-triage

4-phase PR backlog management with audit, deep code review, validated comments, and optional worktree setup. Use when triaging pull requests, catching up on pending code reviews, or managing a backlog of open PRs. Args: 'all' to review all, PR numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit…

FlorianBruniaux/claude-code-plugins · 86 tokens