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/monkilabs/opencastle/exponpx skills add monkilabs/opencastle --skill expogit clone --depth 1 https://github.com/monkilabs/opencastleWrote 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/monkilabs/opencastle/expo)<a href="https://agentmods.dev/skills/monkilabs/opencastle/expo"><img src="https://agentmods.dev/badge/skills/monkilabs/opencastle/expo.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.00069 | $0.00523 |
| Opus 5 | $0.00034 | $0.00262 |
| Sonnet 5 | $0.00014 | $0.00105 |
| Haiku 4.5 | $0.00007 | $0.00052 |
Grade A, and why
expo-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 5d 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.
What it actually says
Expo Development
Continuous Native Generation
- Never eject, never edit
ios/orandroid/—npx expo prebuildregenerates both fromapp.json/app.config.ts, so hand edits vanish. Gitignore both directories.npx expo prebuild --cleanwhen native state is suspect. - Native config changes go through config plugins (
app.plugin.js, registered inexpo.plugins) applied at prebuild time.npx create-expo-modulescaffolds a Swift + Kotlin module. - Install with
npx expo install, notnpm install, so versions resolve against the SDK.npx expo install --fixrepairs an SDK version mismatch.
EAS Build / Update
eas.jsonprofiles: development =developmentClient: true+distribution: internal; preview =distribution: internal+channel; production =channel+autoIncrement: true.- Set
runtimeVersion: { policy: "fingerprint" }in app.json.eas update --channel productionships JS only — a runtimeVersion mismatch forces a new binary build, and native changes can never go OTA. - Rollback:
eas update:republish --group <previous-group-id>. Diagnose failures viaeas build:listtheneas build:view <id>. - Secrets belong in EAS Secrets (
eas secret:create), neverapp.json; device-side storage viaexpo-secure-store. - iOS signing failures:
eas credentials. CI/CD lives in.eas/workflows/.
Expo Router
Files under app/ are routes; a _layout.tsx per directory supplies <Stack> / <Tabs> / <Drawer>. Parenthesized directories are groups and do not appear in the URL — app/(auth)/login.tsx serves /login. Read dynamic segments with useLocalSearchParams(). Deep links require scheme in app.json; myapp://user/123 then resolves to app/user/[id].tsx.
Docs: https://docs.expo.dev/
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.
- 5d ago First seen · 27 lines · 69 tokens per session scan A 9bd50a625c09
expo-development is a skill published in the GitHub repository monkilabs/opencastle (61 stars, last pushed 7d ago), licensed MIT. It adds 69 tokens to every session and 523 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-30.
Other skills, from other repositories
architecture-react-nextjs
Master of React and Next.js performance and rendering architecture. Enforces server/client boundaries, waterfall elimination, and render optimization.
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.
create-react-native-library
Scaffolds React Native libraries with create-react-native-library for standalone libraries or local native modules and views. Use when creating or working on React Native libraries or adding native functionality in an existing app.
mobiai-react-native
Use when working on a React Native project — building, testing, debugging, understanding navigation and state management.
engineer-react-native
Build, refactor, debug, test, and ship production React Native applications across iOS and Android, including Expo and bare workflows. Use for native navigation, app lifecycle, permissions, deep links, secure storage integration, virtualized lists, keyboard and safe-area behavior, gestures, animation, JS/UI thread…
react-navigation
Provides React Navigation UI patterns for stacks, tabs, drawers etc. Use when building navigation UIs with React Navigation, configuring headers, bottom sheets or handling safe areas and insets.