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-api-integrationgit 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-api-integration)<a href="https://agentmods.dev/skills/cmaranho/rn-agent-skills/rn-api-integration"><img src="https://agentmods.dev/badge/skills/cmaranho/rn-agent-skills/rn-api-integration/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-api-integration"><img src="https://agentmods.dev/badge/skills/cmaranho/rn-agent-skills/rn-api-integration.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.00055 | $0.00467 |
| Opus 5 | $0.00028 | $0.00234 |
| Sonnet 5 | $0.00011 | $0.00093 |
| Haiku 4.5 | $0.00006 | $0.00047 |
Grade A, and why
rn-api-integration 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 8d 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 — Integração com APIs
Objetivo
Consumir APIs de forma tipada e resiliente, isolando IO da regra de negócio.
Quando utilizar
- Adicionar chamada a um endpoint.
- Tratar status codes, erros de rede e offline.
- Modelar DTOs, mappers e repositórios.
Conhecimentos necessários
- Cliente HTTP (ex.: fetch/Axios) e interceptors (auth, retry).
- Mapeamento de status code → erro de domínio tipado.
- Padrão Repository e resultado tipado (sucesso/erro).
- Cache/estado de servidor (ex.: React Query) quando aplicável.
Fluxo de execução
- Defina DTOs de request/response e o model de domínio.
- Implemente a chamada no repositório; mapeie cada status code relevante.
- Retorne resultado tipado (
{ ok, data } | { ok: false, error }ouEither); não lance exceção crua. - Normalize DTO → model com mapper puro.
- Consuma via caso de uso; trate loading/erro/sucesso no estado.
Boas práticas
- Auth/refresh e headers comuns em interceptor central.
- Timeout, cancelamento (AbortController) e retry idempotente.
- Erros de domínio tipados carregam contexto.
- Nunca vaze a resposta crua do cliente para a UI.
Armadilhas comuns
- Chamada de API direto no componente/hook de tela.
- Tratar só o caminho feliz; ignorar 4xx/5xx/offline.
anyem respostas; ausência de validação de payload.- Segredos no cliente ou em log.
Critérios de sucesso
- Toda resposta e erro mapeados e tipados.
- Falhas de rede tratadas com estado de erro e recuperação.
- Camada de dados testada (sucesso e erro).
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.
- 8d ago First seen · 52 lines · 55 tokens per session scan A 3a00f4aa4375
rn-api-integration is a skill published in the GitHub repository cmaranho/rn-agent-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 55 tokens to every session and 467 once invoked, about $0.0003 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-31.
Other skills, from other repositories
build-zoom-contact-center-app
Reference skill for Zoom Contact Center. Use after routing to a contact-center workflow when implementing app, web, or native integrations; engagement context and state handling; campaigns; callbacks; or version-drift troubleshooting.
add-signal
Add Signal channel integration via signal-cli device-link. Native adapter — no Chat SDK bridge.
build-zoom-meeting-app
Build or embed a Zoom meeting flow. Use when implementing Meeting SDK joins, web or mobile meeting embeds, meeting lifecycle flows, or when deciding between Meeting SDK and Video SDK.
feature-flag-policy
Cargo feature flags for crates/xberg — ORT-incompatible targets (WASM, Android x8664 emulator), type-only and tract inference companion features, WASM/Android-safe variants, PDF backend, mutually-exclusive ORT variants, platform-conditional deps, aggregate feature sets, and build profiles. Load when adding, wiring, or…
flutter-use-http-package
Use the http package to execute GET, POST, PUT, or DELETE requests. Use when you need to fetch from or send data to a REST API.
at_client_skills-sdk
Use this skill when a developer is building a Dart or Flutter app that depends on atclient or atclientflutter from pub.dev, stores or shares data via the Atsign Protocol, needs onboarding (CRAM new-atsign, atKeys file, keychain, APKAM) or APKAM enrollment, or asks about AtCollection , CItem , Query , sub-collections…