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 cmaranho/rn-agent-skills --skill rn-debugginggit clone --depth 1 https://github.com/cmaranho/rn-agent-skillsWrote 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/cmaranho/rn-agent-skills/rn-debugging)<a href="https://agentmods.dev/skills/cmaranho/rn-agent-skills/rn-debugging"><img src="https://agentmods.dev/badge/skills/cmaranho/rn-agent-skills/rn-debugging/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/cmaranho/rn-agent-skills/rn-debugging"><img src="https://agentmods.dev/badge/skills/cmaranho/rn-agent-skills/rn-debugging.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.00050 | $0.00470 |
| Opus 5.5 | $0.00020 | $0.00188 |
| Sonnet 5.5 | $0.00010 | $0.00094 |
| Haiku 4.5 | $0.00005 | $0.00047 |
Grade A, and why
rn-debugging 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
React Native — Debug
Objetivo
Encontrar a causa raiz de um problema com evidência, não por suposição, e corrigir com o menor blast radius.
Quando utilizar
- Crash, erro em runtime, tela branca ou comportamento divergente.
- Bug reproduzível apenas em um SO/dispositivo.
- Regressão após mudança de dependência nativa.
Conhecimentos necessários
- Ferramentas de debug (ex.: Flipper, Hermes/Chrome debugger, React DevTools, Logcat/Console).
- Leitura de stack trace JS e nativo; source maps.
- Diferenças de plataforma (permissões, APIs nativas, layout).
- Reprodução determinística e bissecção.
Fluxo de execução
- Reproduza de forma confiável; anote passos, plataforma e versão.
- Colete evidência: logs, stack trace, estado e tráfego de rede.
- Forme uma hipótese e isole (bissecção, desabilitar partes, repro mínimo).
- Confirme a causa raiz com evidência antes de corrigir.
- Corrija no ponto certo; valide o cenário e os adjacentes; previna regressão com teste.
Boas práticas
- Uma variável por vez; mude o mínimo para testar a hipótese.
- Reproduza em ambos os SOs quando o bug for de UI/nativo.
- Preserve source maps para builds de release.
- Registre a causa raiz e a correção.
Armadilhas comuns
- "Corrigir" o sintoma sem entender a causa.
- Testar só no simulador (esconde bugs de dispositivo/permissão).
- Assumir sem reproduzir; alterar muitas coisas de uma vez.
- Ignorar logs nativos em crashes nativos.
Critérios de sucesso
- Causa raiz identificada com evidência.
- Bug não reproduz mais; sem regressão introduzida.
- Teste ou guarda adicionado quando aplicável.
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 First seen · 52 lines · 50 tokens per session scan A 8d3dac760e47
rn-debugging is a skill published in the GitHub repository cmaranho/rn-agent-skills (2 stars, last pushed 3mo ago), licensed MIT. It adds 50 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
ios-fix
Autonomous iOS bug fixer. (gstack).
node-connect
Diagnose OpenClaw Control UI browser and native Android, iOS, or macOS node connection failures across route, auth, pairing, QR/setup-code, and reconnect states.
google-mobile-ads-validate
Validates a project's Google Mobile Ads (GMA) SDK integration for iOS, Android, or Unity projects. Use when conducting a full pre-launch audit of an app that integrates GMA SDK or when validating any individual GMA SDK integration checks, such as when validating ad unit IDs and ad formats, SKAdNetwork IDs, mediation…
jetpack-compose-performance
Diagnose and optimize Android Jetpack Compose UI code. Use this skill when analyzing performance bottlenecks of existing code to minimize recomposition overhead and prevent dropped frames and UI lag.
swiftui-performance-audit
SwiftUI performance: render, scroll, CPU/memory, updates, layout, Instruments.
android-tombstone-symbolication
Symbolicate the .NET runtime frames in an Android tombstone file. Extracts BuildIds and PC offsets from the native backtrace, downloads debug symbols from the Microsoft symbol server, and runs llvm-symbolizer to produce function names with source file and line numbers. USE FOR triaging a .NET MAUI or Mono Android app…