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 AnilBurcu/claude-code-react-native --skill fix-buildgit clone --depth 1 https://github.com/AnilBurcu/claude-code-react-nativeWrote 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/anilburcu/claude-code-react-native/fix-build)<a href="https://agentmods.dev/skills/anilburcu/claude-code-react-native/fix-build"><img src="https://agentmods.dev/badge/skills/anilburcu/claude-code-react-native/fix-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/anilburcu/claude-code-react-native/fix-build"><img src="https://agentmods.dev/badge/skills/anilburcu/claude-code-react-native/fix-build.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.00040 | $0.00470 |
| Opus 5.5 | $0.00016 | $0.00188 |
| Sonnet 5.5 | $0.00008 | $0.00094 |
| Haiku 4.5 | $0.00004 | $0.00047 |
Grade A, and why
fix-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 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.
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
Fix the failing native build. Work the problem, do not shotgun it.
-
Identify the project shape first: Expo with CNG (no committed native folders, or folders marked generated), bare workflow, or plain React Native. Check for
app.json/app.config.*,eas.json, and whetherios/andandroid/are committed. -
Reproduce the failure and capture the full log:
- If the user provided a platform in
$ARGUMENTS, build that one. Otherwise ask which platform failed, or build the one whose error the user pasted. - Expo projects:
npx expo run:ios/npx expo run:android(orcd ios && pod installfirst when pods are the suspect) - Plain React Native without the expo package:
npx react-native run-ios/npx react-native run-android - Pipe output to a file so nothing scrolls away.
- If the user provided a platform in
-
Find the FIRST real error in the log, not the last line. Android: deepest
Caused by:. iOS: firsterror:line and the build step above it. Quote the exact error to the user in one line before fixing anything. -
Apply the native-build-errors skill's playbook for that error family. Choose the smallest fix that addresses the cause. Cache cleaning goes in the documented order, never as step one, and each destructive step gets stated before it runs.
-
If the error names a third-party library, search its GitHub issues for the exact error string plus the React Native version before patching anything locally.
-
Rebuild to verify. A fix without a green rebuild is a guess. If the rebuild surfaces a NEW first error, that is progress; repeat from step 3.
-
Close with a short report: root cause, what changed, and whether the fix has release implications (a new native dependency or config change means the next release must be a store build, not an OTA update).
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.
- 1mo ago Changed · -2 tokens per session 76f01cae75c4
- 1mo ago First seen · 26 lines · 42 tokens per session scan A 29384f628af5
fix-build is a skill published in the GitHub repository AnilBurcu/claude-code-react-native (3 stars, last pushed 1mo ago), licensed MIT. It adds 40 tokens to every session and 470 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
expo-56
Authoritative, version-pinned reference for Expo SDK 56 and SDK 57 — both postdate your training, so defer to this skill over memory for anything Expo. SDK 57 is the current release (2026-07-08, React Native 0.86); SDK 56 is the previous, still-supported release (React Native 0.85). Use it whenever the user is…
audit-ppmplugin
Statically audit a built .ppmplugin before wrap testing. Checks archive layout, manifest compatibility, bundle consistency, Android DEX integrity and SDK leakage, iOS framework structure, native source-to-receiver alignment, and the PCF composite-key/sendAsync transport contract. Reports CRITICAL, WARNING, and INFO…
generate-ppmplugin-manifest
Validate, reconcile to the chosen target(s), and stage the manifest.json for a .ppmplugin bundle. In the normal flow the committed ./manifest.json already exists (authored by /generate-native-extension), so this stage reads it, runs the plugin's upload-compatibility checks locally as a pre-flight gate (name regex…
expo
Use when shipping a React Native app with Expo — EAS Build/Submit/Update, eas.json profiles and channels, config plugins, prebuild/CNG, runtime-version policy, OTA updates that never land, SDK upgrades, the New Architecture. NOT RN UI, navigation or native-module authoring (that is react-native), NOT a Dart app (that…
touch-audit
Mobile audit — app size, startup time, crash reporting, store compliance, accessibility, offline behavior. Use when asked for "mobile review", "app store readiness", "mobile performance", or "crash analysis".
performance-profiling
Instruments integration and performance analysis workflows for iOS apps. Use when profiling CPU usage, memory allocation, network activity, or energy consumption. Covers Time Profiler, Allocations, Leaks, Network instruments, and performance optimization strategies.