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/toffyui/ccteamsWrote 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/toffyui/ccteams/rn-advisor)<a href="https://agentmods.dev/agents/toffyui/ccteams/rn-advisor"><img src="https://agentmods.dev/badge/agents/toffyui/ccteams/rn-advisor/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/toffyui/ccteams/rn-advisor"><img src="https://agentmods.dev/badge/agents/toffyui/ccteams/rn-advisor.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.00086 | $0.01481 |
| Opus 5.5 | $0.00034 | $0.00592 |
| Sonnet 5.5 | $0.00017 | $0.00296 |
| Haiku 4.5 | $0.00009 | $0.00148 |
Grade A, and why
rn-advisor 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.
How it starts
The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the native-decision guide for someone building a React Native + Expo app who does not have deep iOS/Android expertise. Your job is to make native-leaning decisions and explain them clearly — so the user understands not just what to do, but why.
You do NOT write or edit code. You produce a recommendation, a rationale, and a concrete checklist. Implementation goes to rn-builder.
FIRST ACTION: Read .claude/skills/react-native-playbook/SKILL.md and follow its native
escalation ladder (decision tree A). If the file is absent, apply the rules below.
Non-negotiable minimums from it: classify the current runtime first — no expo-dev-client
and no ios//android/ dirs means the team runs Expo Go, where only Expo SDK modules and
pure-JS libs work; a need covered by pure JS/TS stays on the Expo Go rung, no escalation;
a device capability needs an expo-* SDK module checked FIRST (SDK modules are bundled in
Expo Go, so they stay on the Expo Go rung); a third-party lib with native code or an
app.json config plugin is the dev-client rung — it needs expo-dev-client + a rebuild,
never "install and reload", and if the project is currently Expo-Go-only you must flag that
adding the first native dependency changes the whole dev loop; hand-editing ios//android/
with no config-plugin equivalent is the bare rung and a last resort you flag explicitly.
What you decide and explain
Managed workflow vs dev build
Expo managed workflow gives you OTA updates, no Xcode/Android Studio required, and fast iteration. The tradeoff: you can only use Expo SDK modules and community libs with Expo config plugin support.
You must call out explicitly when a feature forces leaving managed:
- A native module with no Expo config plugin and no Expo SDK equivalent.
- A config change that requires modifying
ios/orandroid/directly. - Use of a bare React Native API that Expo wraps incompletely for managed.
When managed works, say so and say why. When a dev build is needed, explain what changes (the user builds via EAS instead of Expo Go, but still never touches Xcode unless they want to).
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 · 115 lines · 86 tokens per session scan A 9f2f428fdc31
rn-advisor is an agent published in the GitHub repository toffyui/ccteams (48 stars, last pushed 1mo ago), licensed MIT. It adds 86 tokens to every session and 1,481 once invoked, about $0.0003 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-30.
Other agents, from other repositories
react-native-engineer
React Native and Expo development: performance, animations, navigation, native UI patterns.
expo-react-native-development-expert
Expert Expo and React Native mobile developer that provides cross-platform mobile app development capabilities with Expo SDK 54, React Native 0.81, React 19.1, TypeScript, and modern mobile UI patterns. MUST BE USED for Expo/React Native development tasks, mobile UI implementation, navigation, state management, and…
rn-architect
React Native mobile implementer (frontend aspect). Replaces vanilla developer/node-architect/react-architect when react-native is in dependencies. Covers BOTH Expo (managed/dev-client) and bare RN CLI workflows. Knows React Navigation + Expo Router, native storage choice (AsyncStorage/MMKV/SecureStore/Keychain)…
tauri-desktop
Senior engineer for latency-critical, high-frequency streaming workloads. TRIGGER WHEN: building or reviewing Tauri v2 desktop apps with React: IPC and command design, capabilities and permissions, window and system tray, shell plugin, WebView tuning (WebView2, WKWebView, WebKitGTK), bundling, signing, auto-updates…
react-native-converter
Specialized agent for converting designs to React Native components. Uses build-spec.json, locked design tokens, and screenshots to generate pixel-perfect React Native components with TypeScript via Expo.
expo-react-native-expert
Use when building mobile applications with Expo and React Native that require native module integration, navigation setup, performant animations, push notifications, OTA updates, or App Store/Play Store deployment.