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 suntay44/web-to-mobile-magic-plugin --skill expo-react-native-buildgit clone --depth 1 https://github.com/suntay44/web-to-mobile-magic-pluginWrote 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/suntay44/web-to-mobile-magic-plugin/expo-react-native-build)<a href="https://agentmods.dev/skills/suntay44/web-to-mobile-magic-plugin/expo-react-native-build"><img src="https://agentmods.dev/badge/skills/suntay44/web-to-mobile-magic-plugin/expo-react-native-build/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/suntay44/web-to-mobile-magic-plugin/expo-react-native-build"><img src="https://agentmods.dev/badge/skills/suntay44/web-to-mobile-magic-plugin/expo-react-native-build.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 27 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 27 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 28 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00038 | $0.00607 |
| Opus 5 | $0.00019 | $0.00303 |
| Sonnet 5 | $0.00008 | $0.00121 |
| Haiku 4.5 | $0.00004 | $0.00061 |
Grade A, and why
expo-react-native-build 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 today.
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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Expo React Native Build
Required Gates
Before editing code, confirm:
- A plan exists under
docs/web-to-mobile/(migration) ordocs/mobile-resume/(completion). - The plan has an Implementation Checklist.
- The user approved implementation — if not, return to
mobile-migration-planormobile-completion-plan. - The approved stack is Expo React Native; otherwise use the plan's handoff.
Pre-Build Validation
Before screen/component code, verify:
app.jsonhasname,slug, andversionset.npx expo-doctorandnpx expo install --checkpass. Usenpx expo install --fixfor dependency alignment; plan SDK upgrades instead of silently changing major versions.- Referenced environment variables appear in
.env.exampleor the plan. - If the plan targets EAS Build,
eas.jsonexists with at least one build profile.
If a required value is missing, add it to the plan's Unknowns/Blockers section and ask the user before continuing.
Build Rules
- Read the checklist, approval, blockers, and sections needed for the current item. Reuse unchanged context; do not reload the full plan per edit.
- Skip
- [x]items. Implement only- [ ]items. - Keep changes scoped to the approved plan.
- Follow the plan's reuse/rewrite decisions and mobile-native gaps.
- Use the source repo's package manager and style.
- Reuse TypeScript types, API clients, validation schemas, state patterns, assets, and non-DOM business logic where practical.
- Rewrite DOM components, CSS-dependent UI, browser storage, cookies, and OAuth redirects for mobile.
- For web dependency replacements, read the matching entries in
../mobile-migration-plan/references/dependency-substitutions.md. - Update checklist items from
- [ ]to- [x]when their done condition is verified. Record command, exit code, and key output once; reference shared results. - Update the plan with deviations, blockers, and the next unblocked item at handoff.
Expo Implementation Guidance
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.
- today Changed · -11 lines 5e49b8e90e2c
- 9d ago First seen · 74 lines · 38 tokens per session scan A 863ee43e4e06
expo-react-native-build is a skill published in the GitHub repository suntay44/web-to-mobile-magic-plugin (106 stars, last pushed yesterday), licensed MIT. It adds 38 tokens to every session and 607 once invoked, about $0.0002 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
expo-native-ui
Framework (OSS). Build beautiful, native-feeling Expo screens. Covers Apple HIG styling, semantic colors, native controls, SF Symbols, media, visual effects, gradients, storage, and responsive layout. For routing and navigation, use the expo-router skill; for motion and animation, use the expo-animation 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…
truesheet-usage
Consumer-side guide for integrating @lodev09/react-native-true-sheet into a React Native app. Use this skill whenever the user wants to add, configure, control, or debug a bottom sheet using TrueSheet — including ref-based sheets, named global sheets, web support with TrueSheetProvider/useTrueSheet, React Navigation…
building-ui
Complete guide for building beautiful apps with Expo Router. Covers fundamentals, styling, components, navigation, animations, patterns, and native tabs.
use-dom
Use Expo DOM components to run web code in a webview on native and as-is on web. Migrate web code to native incrementally.
react-native
React Native mobile patterns, platform-specific code.