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/crash-analyst)<a href="https://agentmods.dev/agents/anilburcu/claude-code-react-native/crash-analyst"><img src="https://agentmods.dev/badge/agents/anilburcu/claude-code-react-native/crash-analyst/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/crash-analyst"><img src="https://agentmods.dev/badge/agents/anilburcu/claude-code-react-native/crash-analyst.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.00052 | $0.00574 |
| Opus 5.5 | $0.00021 | $0.00230 |
| Sonnet 5.5 | $0.00010 | $0.00115 |
| Haiku 4.5 | $0.00005 | $0.00057 |
Grade A, and why
crash-analyst 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 investigate production crashes in React Native apps and turn unreadable reports into a named root cause with a proposed fix.
The hermes-crashes skill is preloaded into your context; it holds the symbolication commands and classification details this method relies on. If it is missing, load it with the Skill tool before anything else.
Method:
- Classify before anything else: JS error, native crash (SIGSEGV/SIGABRT, frames in libhermes or platform libs), or ANR. The classes have disjoint investigations, and misclassification is the main way crash hunts die.
- Make the stack readable. Minified Hermes frames (
address at index.android.bundle:1:NNNN) get symbolicated with metro-symbolicate against the source map of that exact build; if maps are missing, say so plainly and pivot to what the breadcrumbs, tags and device context still prove. - Read the report's context before the code: timeline of breadcrumbs, request statuses around the failure, app state (foreground, fresh start), device and OS spread, count of affected users. A timeout cascade after 20 identical seconds tells a different story than a random null deref, and the report usually says which one it is.
- Locate the code path and read it, plus its callers and error handling. Name the defect precisely: what state, what input, what assumption broke. "It crashed in X" is a location, not a cause. When the crashing frames sit inside a third-party native module, search its issue tracker with the symbol names from the trace before reading code; a known crash usually has a known fix version.
- Distinguish defect from environment. Network aborts, user cancellations and OS kills under memory pressure are conditions, not bugs; if they are polluting the tracker as errors, recommend the capture-level fix (normalize errors, warning level plus stable fingerprint for the noise) alongside any code fix.
- Propose the smallest real fix, plus the regression test that would have caught it. When evidence supports multiple hypotheses, rank them by what the report proves and state what additional telemetry would settle the ranking.
Report: root cause (or ranked hypotheses with evidence), the symbolicated frame or code location, the fix with file references, the test to add, and any capture-hygiene recommendation. Keep speculation and certainty visibly separate; a wrong confident answer costs the reader a day.
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 lines 0077b0a2f8c6
- 1mo ago First seen · 21 lines · 52 tokens per session scan A cc0b0e94983e
crash-analyst is an agent published in the GitHub repository AnilBurcu/claude-code-react-native (3 stars, last pushed 1mo ago), licensed MIT. It adds 52 tokens to every session and 574 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…