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-app-publishinggit 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-app-publishing)<a href="https://agentmods.dev/skills/cmaranho/rn-agent-skills/rn-app-publishing"><img src="https://agentmods.dev/badge/skills/cmaranho/rn-agent-skills/rn-app-publishing/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-app-publishing"><img src="https://agentmods.dev/badge/skills/cmaranho/rn-agent-skills/rn-app-publishing.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.00462 |
| Opus 5 | $0.00025 | $0.00231 |
| Sonnet 5 | $0.00010 | $0.00092 |
| Haiku 4.5 | $0.00005 | $0.00046 |
Grade A, and why
rn-app-publishing 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.
What it actually says
React Native — Publicação de Aplicações
Objetivo
Entregar builds de release assinados e conformes nas lojas, de forma repetível.
Quando utilizar
- Gerar build de produção (AAB/IPA).
- Submeter/atualizar app na App Store ou Play Store.
- Configurar assinatura, versionamento e metadados.
Conhecimentos necessários
- Assinatura: keystore (Android), certificados/provisioning (iOS).
- Formatos e identificadores: AAB/APK, IPA; bundle id/application id.
- Versionamento: versionName/versionCode, CFBundleShortVersionString/Build.
- Requisitos das lojas (privacidade, permissões, ícones, screenshots).
Fluxo de execução
- Incremente versão (nome + build) de forma consistente entre plataformas.
- Selecione o ambiente/variante de produção e as variáveis corretas.
- Gere o build de release assinado (idealmente via CI/fastlane).
- Teste o build de release em dispositivo (não só debug/simulador).
- Submeta com metadados/conformidade; distribua por canal (beta → produção).
Boas práticas
- Automatize versionamento e assinatura no CI.
- Valide permissões e política de privacidade antes de submeter.
- Distribua primeiro em canal interno/beta.
- Habilite ofuscação/minificação e desabilite debug em release.
Armadilhas comuns
- Publicar build de debug ou com env de desenvolvimento.
- versionCode/build number não incrementado → rejeição.
- Perda de keystore/certificado de assinatura.
- Permissões não declaradas ou política de privacidade ausente.
Critérios de sucesso
- Build de release assinado, testado em dispositivo e aceito pela loja.
- Versionamento consistente e rastreável.
- Processo repetível e majoritariamente automatizado.
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 · 52 lines · 50 tokens per session scan A c27f5503b89e
rn-app-publishing is a skill published in the GitHub repository cmaranho/rn-agent-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 50 tokens to every session and 462 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
axiom-shipping
Use when preparing ANY app for submission, handling App Store rejections, writing appeals, or managing App Store Connect. Covers submission checklists, rejection troubleshooting, metadata requirements, privacy manifests, age ratings, export compliance.
asc-ad-hoc-distribution
Prepare, publish, resume, and verify private iOS release-testing installs with asc distribute. Use when distributing an IPA to registered devices outside TestFlight, reconciling ad hoc profiles, publishing through caller-owned S3-compatible storage, or diagnosing a resumable private distribution run.
release-new-version
Use when the user wants to release a new Zafiro version — drafting bilingual release notes, deciding the next version number, bumping app/build.gradle.kts, tagging, and publishing to GitHub (main repo, optionally the Xposed repo).
suede-play-release
Suede Labs Google Play delivery skill: ship an Android release end to end from the agent interface, without opening the Play Console. Set up credentials, upload an AAB, promote between tracks, stage or complete a rollout, push per-locale release notes, and prove against the Play Developer API what is actually live.…
testflight-release
Ship a new TestFlight build of the iOS companion (TermioMobile) — resolve the next build number against App Store Connect, archive, sign, export, upload, write the What to Test notes, and distribute. Invoke when the user says 'ship a testflight build', 'update testflight', 'upload to testflight', 'new beta build'…
app-release
End-to-end pipeline for releasing an iOS / watchOS app to TestFlight and the App Store. Use when the user wants to publish, ship, or release an iOS/watchOS app, get a build onto TestFlight, archive and upload via xcodebuild, deploy a CloudKit schema to Production, set App Privacy or export compliance, mint a…