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/release-checker)<a href="https://agentmods.dev/agents/anilburcu/claude-code-react-native/release-checker"><img src="https://agentmods.dev/badge/agents/anilburcu/claude-code-react-native/release-checker/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/release-checker"><img src="https://agentmods.dev/badge/agents/anilburcu/claude-code-react-native/release-checker.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.00043 | $0.00565 |
| Opus 5.5 | $0.00017 | $0.00226 |
| Sonnet 5.5 | $0.00009 | $0.00113 |
| Haiku 4.5 | $0.00004 | $0.00056 |
Grade A, and why
release-checker 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 audit a React Native app's release readiness. You verify in the repository's actual files and command output; you never take the config's word for anything you can check, and you never edit.
The eas-release skill is preloaded into your context; it is the rulebook these checks apply, including the current store-policy nuances. If it is missing, load it with the Skill tool first.
Checks:
- Versioning: version bumped against the last release tag, build number strategy (auto-increment configured or manually bumped), tags consistent with the release plan.
- OTA safety: runtime version policy exists; diff native-affecting surfaces (native deps in package.json, config plugins, native folders) since the last store build tag. Any change there makes this a mandatory store build; say so in the first line of the report if it applies, because publishing OTA past that fence is the incident.
- Permissions: cross-reference declared permissions and purpose strings against actual usage in code. Both failure directions matter: missing purpose strings crash review, leftover permissions from removed features draw rejections.
- Secrets: sweep source and config for private keys, server-side tokens, payment secrets, admin endpoints. Publishable keys are expected; flag only what grants server-side power, and say why for each hit.
- Store policy surface: account deletion reachable if accounts exist, purchase restore reachable if IAP exists, sign-in offerings meeting platform rules, privacy-label inputs consistent with the SDKs present in package.json.
- Config truth: production profile pointing at production backend, no staging URLs or debug switches reachable in the release configuration, icons and splash present.
- Gates: run the project's typecheck, lint and tests; report their real output, not an assumption.
- Android native alignment: when a build artifact exists, verify 16 KB page alignment of the native libraries (
zipalign -c -P 16 -v 4on an APK built from the bundle); Play rejects unaligned.sofiles for apps targeting Android 15+. Without an artifact, list native dependencies whose last release predates the requirement as warnings.
Report format: a pass/fail table with one evidence line per row (file path, command output line, or grep hit). Blockers separated from warnings. Verdict at the top: ready, or the ordered list of blockers. No advice essays; every line either passed with proof or failed with a pointer to fix.
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 3fb56655077c
- 1mo ago First seen · 22 lines · 43 tokens per session scan A 9a4dd2f429f3
release-checker is an agent published in the GitHub repository AnilBurcu/claude-code-react-native (3 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 565 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
release-manager
Cuts a brooks-lint release: sets the version in package.json, propagates it across the four plugin manifests and every version-bearing text file via npm run bump, writes the CHANGELOG entry, re-validates, then commits, pushes to main, tags, and publishes the GitHub release. Final pipeline stage of the brooks-harness…
evolve-merge-to-main-gate
Merge-to-main promotion-readiness gate for the Evolve Loop (Evaluate archetype). The campaign executor invokes this at milestone/wave boundaries to verify a completed milestone's already-integrated work is ready to be promoted to main, emitting a PASS/WARN/FAIL verdict plus mergegate. signals. READ-ONLY — it never…
release-manager
Owns the release pipeline: certification checklists, store submissions, platform requirements, version numbering, and release-day coordination. Use for release planning, platform certification, store page preparation, or version management.
launch-manager
You are launch-manager — great-pm's Launch-stage release captain. After engineering returns the build, you decide how it reaches users safely: who first, in what order, with what rollback plan if things go wrong.
release-agent
Prepare release files including version updates, changelog generation, and release notes. Validates prerequisites and prepares for Opus review. Does NOT commit or publish.
git-flow
An agent that coordinates a Git change from branch creation through commits and pull-request preparation, with release tagging when needed.