Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/fatihkan/badinpx agentmods add skills/fatihkan/badi/expo-troubleshootingWrote 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-troubleshooting)<a href="https://agentmods.dev/skills/fatihkan/badi/expo-troubleshooting"><img src="https://agentmods.dev/badge/skills/fatihkan/badi/expo-troubleshooting/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-troubleshooting"><img src="https://agentmods.dev/badge/skills/fatihkan/badi/expo-troubleshooting.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.00000 | $0.02081 |
| Opus 5 | $0.00000 | $0.01040 |
| Sonnet 5 | $0.00000 | $0.00416 |
| Haiku 4.5 | $0.00000 | $0.00208 |
Grade C, and why
expo-troubleshooting 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 4d 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/.cache .expo How it starts
The opening of the file, as written. The whole thing — 344 lines — stays where its author put it; the contents beside it link to each section on GitHub.
expo-troubleshooting
Common error patterns and fix recipes in Expo + React Native projects. Metro cache, version mismatch, native build errors, reading EAS Build logs, and dependency conflicts.
What It Does
- Metro bundler cache-clearing recipe
- Health check with
expo-doctorandexpo install --check - iOS Pod install errors (mismatch, cache, deployment target)
- Android Gradle daemon, cache, multiDex
- Native module conflicts and autolinking problems
- A guide to reading EAS Build logs
- Monorepo dependency hoisting problems
Quick Health Check
npx expo-doctor
npx expo install --check
npx expo install --fix # auto-fix incompatibilities
expo-doctor checks these areas:
- SDK version compatibility
- Package version mismatch
- Plugin configuration
- Network access
- Native file consistency
Metro Cache Problems
Symptom: "Module not found", stale JS, a new file isn't picked up.
# Quick
npx expo start --clear
# Deeper
rm -rf node_modules/.cache .expo
watchman watch-del-all
npm cache clean --force
rm -rf $TMPDIR/metro-*
rm -rf $TMPDIR/haste-map-*
# Reset
rm -rf node_modules
npm install
npx expo start --clear
watchman problem:
watchman shutdown-server
brew install --HEAD watchman # macOS
Version Mismatch
Symptom: "[email protected] is not compatible with expo@51"
npx expo install --check
# > "[email protected] is incompatible. Expected: X.Y"
npx expo install --fix
# or by hand
npx expo install react-native react react-dom
Manual inspection:
npx expo install --check --json
iOS Pod Install Errors
Error: "CocoaPods could not find compatible versions"
cd ios
pod repo update
pod deintegrate
rm -rf Pods Podfile.lock
pod install --repo-update
Error: "Deployment target ... but pod requires iOS 15.1"
app.json:
{
"expo": {
"plugins": [
["expo-build-properties", {
"ios": { "deploymentTarget": "15.1" }
}]
]
}
}
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.
- 4d ago First seen · 344 lines · 0 tokens per session scan C a80a692342cd
expo-troubleshooting is a skill published in the GitHub repository fatihkan/badi (7 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,081 tokens. 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
issue-triage
3-phase issue backlog management with audit, deep analysis, and validated triage actions. Use when triaging GitHub issues, sorting bug reports, cleaning up stale tickets, or detecting duplicate issues. Args: 'all' to analyze all, issue numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit only.
check-cache-bugs
Audit Claude Code setup for cache bugs (CC#40524): sentinel, --resume/--continue, attribution header + ArkNill B3/B4/B5.
eval-rules
Audit .claude/rules/ files for structural correctness, glob validity, and real-world usefulness. Resolves each paths: pattern against actual project files, then asks the user whether each rule is still relevant and useful. Can update rules in-place based on answers. Use when setting up rules for the first time…
audit-codebase
Codebase health audit scoring 7 categories with progression plan.
debugging
Use when encountering any bug, test failure, error, or unexpected behavior - before proposing fixes. Requires root cause investigation first.
diagnose
Interactive troubleshooting assistant for Claude Code issues.