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 agentmods add skills/anilburcu/claude-code-react-native/new-arch-checknpx skills add AnilBurcu/claude-code-react-native --skill new-arch-checkgit 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/skills/anilburcu/claude-code-react-native/new-arch-check)<a href="https://agentmods.dev/skills/anilburcu/claude-code-react-native/new-arch-check"><img src="https://agentmods.dev/badge/skills/anilburcu/claude-code-react-native/new-arch-check.svg" alt="Measured on agentmods" 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 | $0.00037 | $0.00318 |
| Opus 5 | $0.00018 | $0.00159 |
| Sonnet 5 | $0.00007 | $0.00064 |
| Haiku 4.5 | $0.00004 | $0.00032 |
Grade A, and why
new-arch-check 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 4d 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
Audit the project's dependencies for New Architecture readiness and abandonment risk.
-
Read
package.jsonand collect dependencies that ship native code or are React Native specific. Skip pure-JS utility packages; they are not the risk. -
Run
npx expo-doctorand capture what it flags. It checks packages against React Native Directory metadata and catches known-incompatible and unmaintained ones. -
For each remaining native dependency not covered by doctor output, query React Native Directory:
https://reactnative.directory/api/libraries?search=<package-name>Note the New Architecture flag and the last-release recency. A package missing from the directory is not automatically bad, but combined with an old last-publish date it goes in the risk column. -
Produce a single table: package, version, New Architecture status (supported / interop-expected / unsupported / unknown), last release age, and verdict. Three verdicts only:
- keep: maintained and compatible
- watch: works today via interop or unclear, has a pulse; recheck at the next SDK upgrade
- replace: abandoned or incompatible; name the standard replacement (the new-architecture skill lists the usual swaps)
-
End with the two or three highest-risk items and one concrete next step for each. No generic advice; name packages and replacements.
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.
- 4d ago First seen · 22 lines · 37 tokens per session scan A 2a55c5cea9a2
new-arch-check is a skill published in the GitHub repository AnilBurcu/claude-code-react-native (3 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 318 once invoked, about $0.0002 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
expo-56
Authoritative, version-pinned reference for Expo SDK 56 and SDK 57 — both postdate your training, so defer to this skill over memory for anything Expo. SDK 57 is the current release (2026-07-08, React Native 0.86); SDK 56 is the previous, still-supported release (React Native 0.85). Use it whenever the user is…
expo-launchpad-evaluator
Phase A, step 6 — skeptical QA. Run the app, watch it, then judge against the contract. Default = functional check; --strict adds quality scoring and an edge-case sweep.
expo-launchpad-design
Phase A design — define the ui/designTokens.ts spec (colors, spacing, radius, typography), the visual/component concept (game: code-drawn Skia shapes / app: RN primitives), and the asset plan (icon+splash branding, contrast-safe accessibility). Advances pipeline state to contract.
expo-launchpad-plan
Phase A plan — assign app identity (appname/appslug/bundleid/orientation) into config.md, then write the PRD in defaultlanguage with a kind-branched structure (game: core loop/mechanics/content metrics/progression/win-lose; app: purpose/journeys/features/data model/navigation), plus a project structure map, and…
expo-launchpad-contract
Phase A contract — propose the 8 Mandatory Hard Gates, the Platform-Robustness Gates (R1–R11), and 5–10 Functional Criteria derived from the PRD; mark the contract AGREED (1-pass default, rigorous self-review in --strict) and advance the pipeline to generator.
expo-launchpad-research
Phase A research — kind-aware market/genre (game) or category/competitor (app) discovery, concept proposal via AskUserQuestion, a store clone-avoidance check (App Store 4.3 / Google Play impersonation), and the research spec write-up.