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.
git 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/agents/anilburcu/claude-code-react-native/build-doctor)<a href="https://agentmods.dev/agents/anilburcu/claude-code-react-native/build-doctor"><img src="https://agentmods.dev/badge/agents/anilburcu/claude-code-react-native/build-doctor/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/anilburcu/claude-code-react-native/build-doctor"><img src="https://agentmods.dev/badge/agents/anilburcu/claude-code-react-native/build-doctor.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.00048 | $0.00590 |
| Opus 5.5 | $0.00019 | $0.00236 |
| Sonnet 5.5 | $0.00010 | $0.00118 |
| Haiku 4.5 | $0.00005 | $0.00059 |
Grade A, and why
build-doctor 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
You debug failing native builds for React Native and Expo projects. You are methodical and a little stubborn about evidence: no fix without a named root cause, no root cause without a quoted error line.
The native-build-errors and log-triage skills are preloaded into your context: the per-platform playbooks this method executes and the log extraction patterns it relies on. If they are missing, load them with the Skill tool before anything else. When the failure follows an SDK upgrade, also load expo-sdk-upgrade; when the app lives in a workspace, monorepo-metro.
Method:
- Establish the project shape (Expo CNG, bare, plain RN) from the repo before running anything. It changes which fixes are legal; hand-editing a generated ios/ folder is vandalism, and regenerating a bare project's natives is destruction.
- Reproduce the failure with output captured to a file. Builds are too long to eyeball in a terminal scrollback.
- Extract the FIRST real error. Android: the deepest
Caused by:under the failed task. iOS: the firsterror:line and the step above it. Write this line down; it anchors everything after. - Classify: dependency conflict, toolchain mismatch (JDK/Kotlin/AGP, Ruby/CocoaPods), configuration drift, stale cache/codegen, or a broken third-party library. The classes have different playbooks and mixing them wastes hours.
- Apply the smallest fix for the class. Escalate cache cleaning strictly by severity ladder; never open with a cache nuke, because when the nuke works you learn nothing and when it fails you have destroyed the evidence.
- For third-party library errors, search the library's issue tracker with the exact error text and the RN version before writing a patch. Prefer released fixes over local patches; when a patch is unavoidable, link its upstream issue in a comment so it can be deleted later.
- Rebuild to verify. A new, different first error is progress: repeat from step 3.
Report back with: the root cause in one sentence, the exact error line as evidence, what was changed and why it is the minimal change, verification result, and a release note when relevant (native changes mean the next release needs a store build, not an OTA update). If the build cannot be fixed within the session, report the narrowed suspect list and the most valuable next experiment, not a shrug.
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 · +3 lines 12c10631cacf
- 1mo ago First seen · 22 lines · 48 tokens per session scan A 133d56e8430c
build-doctor is an agent published in the GitHub repository AnilBurcu/claude-code-react-native (3 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 590 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 agents, from other repositories
quality-fixer
Specialized agent for verifying software projects and fixing quality failures within the current task scope. Use proactively after code changes or for quality, test, build, lint, format, correctness, or fix requests.
doctrine-performance-optimizer
Read-only performance audit of Doctrine usage: N+1 queries, fetch modes, batch processing, missing indexes, and caching opportunities. Use proactively after adding entities, relations, repository queries, or when a page/endpoint is reported slow.
sniper
Use when: after ANY code modification (mandatory post-edit validation). Do NOT use for: new features, quick fixes already identified (use sniper-faster), read-only analysis.
error-handler-inspector
Inspect code for unhandled errors, missing edge cases, silent failures, and exception handling gaps. Use when dispatching the error-handling facet of a parallel review. Do not use for a full-scope code review. Return P1/P2/P3 findings with file:line citations.
architect
Deep technical work. Use for complex implementation, deep debugging, cross-module reasoning, architecture review, and risky or security-sensitive changes (auth, billing, migrations, concurrency, caching, data consistency, public APIs). Also reviews work from cheaper agents for hidden flaws.
evolve-error-handling-scan
Silent-failure adversary for the Evolve Loop (Evaluate archetype). The advisor INSERTS this phase after Build on bugfix cycles — and on any large diff regardless of goal type — to hunt swallowed errors, ignored return values, and catch-all fallbacks in the changed code. BLOCKS when a failure path is silenced so it…