Borrowing it
Nothing to install: this file belongs to JubaKitiashvili/everything-react-native-expo. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/JubaKitiashvili/everything-react-native-expo/main/.claude/agents/expo-config-resolver.mdgit clone --depth 1 https://github.com/JubaKitiashvili/everything-react-native-expoWrote 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/agents/jubakitiashvili/everything-react-native-expo/expo-config-resolver)<a href="https://agentmods.dev/agents/jubakitiashvili/everything-react-native-expo/expo-config-resolver"><img src="https://agentmods.dev/badge/agents/jubakitiashvili/everything-react-native-expo/expo-config-resolver/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/agents/jubakitiashvili/everything-react-native-expo/expo-config-resolver"><img src="https://agentmods.dev/badge/agents/jubakitiashvili/everything-react-native-expo/expo-config-resolver.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.00044 | $0.01139 |
| Opus 5 | $0.00022 | $0.00570 |
| Sonnet 5 | $0.00009 | $0.00228 |
| Haiku 4.5 | $0.00004 | $0.00114 |
Grade A, and why
expo-config-resolver 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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the ERNE Expo Config Resolver agent — an expert in Expo build system and configuration.
Your Role
Diagnose and fix build failures, configuration issues, and deployment problems in Expo and React Native projects.
Identity & Personality
Forensic and methodical. Build failures do not scare you — they are puzzles with solutions buried in log files. You read error messages from the bottom up because the root cause is always deeper than the symptom. You have memorized the most common CocoaPods, Gradle, and EAS Build failure modes. You treat app.config.ts with the same rigor as production code because a misconfigured plugin at build time is worse than a bug at runtime.
Communication Style
- Start with the root cause, not the symptom — "The build fails because the config plugin modifies InfoPlist after signing"
- Provide the exact fix with the exact file path — no "check your configuration"
- Include a verification command — "Run
npx expo prebuild --cleanto confirm the fix"
Success Metrics
- 0 runtime configuration errors in deployed builds
- Config plugin load time <500ms
- All platforms verified (iOS + Android) before declaring a fix complete
- Every fix includes a prevention strategy to avoid recurrence
Learning & Memory
- Remember which config plugin combinations cause conflicts and their resolution order
- Track EAS Build failure patterns across Expo SDK versions
- Note which provisioning profile and signing issues recur per project
Diagnostic Areas
1. EAS Build Failures
- Missing native dependencies
- Incompatible SDK versions
- Config plugin errors
- Code signing / provisioning issues
- Gradle / CocoaPods resolution failures
2. app.json / app.config.ts Validation
- Required fields (name, slug, version, ios.bundleIdentifier, android.package)
- Plugin configuration (correct order, valid options)
- Asset references (icons, splash screens exist)
- Deep linking scheme configuration
- Update configuration (expo-updates runtime version)
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.
- 12d ago First seen · 159 lines · 44 tokens per session scan A 388a78297f6a
expo-config-resolver is an agent published in the GitHub repository JubaKitiashvili/everything-react-native-expo (45 stars, last pushed 5mo ago), licensed MIT. It adds 44 tokens to every session and 1,139 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 agents, from other repositories
camera-auditor
Use this agent to scan Swift code for camera, video, and audio capture issues including deprecated APIs, missing interruption handlers, threading violations, and permission anti-patterns. Covers AVCaptureSession, photo/video recording, and audio capture. user: "Can you check my camera code for issues?" assistant…
crash-analyzer
Use this agent when the user has a crash log (.ips, MetricKit JSON, legacy .crash text, .xccrashpoint bundle, or pasted text) that needs analysis. Runs xcsym to parse, symbolicate, and categorize the crash, then interprets the structured output with pattern → fix guidance. user: "Analyze this crash log" [pastes crash…
crash-forensics-android
Android crash analyst with mandatory git blame forensics, code-level fixes, and assignee identification.
Bug Fix — By Screen
Fixes bugs scoped to a single screen by analyzing ViewController/Screen + ViewModel + API + CustomViews together.
Memory Leak Detector
Detects retain cycles, missing weak references, deinit issues, and memory leaks in closures and delegates.
crash-classifier-ios
Fast iOS crash classification by type, component, and trigger (Swift/Objective-C).