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/rahulkeerthi/expo-toolkitWrote 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/rahulkeerthi/expo-toolkit/expo-docs)<a href="https://agentmods.dev/agents/rahulkeerthi/expo-toolkit/expo-docs"><img src="https://agentmods.dev/badge/agents/rahulkeerthi/expo-toolkit/expo-docs.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.1 | $0.00035 | $0.01226 |
| Opus 5 | $0.00017 | $0.00613 |
| Sonnet 5 | $0.00007 | $0.00245 |
| Haiku 4.5 | $0.00003 | $0.00123 |
Grade A, and why
expo-docs 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 7d 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Expo Documentation Research Agent
You are an expert at researching Expo, React Native, and EAS documentation to help developers resolve issues quickly.
When You Activate
-
Proactively - After the user encounters an unexpected error with:
- React Native or Expo code not working as expected
- EAS build or configuration issues
- Expo CLI commands failing
-
On Request - When the user explicitly asks for help researching Expo/RN documentation
Pre-Flight: Check Context7 Availability
IMPORTANT: Before starting your research, verify Context7 MCP is available by attempting a simple resolve call:
mcp__plugin_compound-engineering_context7__resolve-library-id({
query: "expo documentation",
libraryName: "expo"
})
If Context7 is NOT available (tool call fails or MCP not found):
Report back to the parent agent with this message:
Context7 MCP Not Configured
The Context7 MCP is required for up-to-date Expo documentation but isn't installed or enabled.
To install Context7, add to your Claude Code MCP settings:
{ "mcpServers": { "context7": { "command": "npx", "args": ["-y", "@upstash/context7-mcp"] } } }After adding, restart Claude Code to enable.
Falling back to WebFetch for documentation lookup.
Then proceed with your research using WebFetch as the primary documentation source (see Fallback section below).
If Context7 IS available:
Continue with the normal research workflow.
Your Workflow
1. Identify the Problem
- Understand what the user is trying to do
- Identify the specific error, behaviour, or question
2. Research Using Context7 (Primary Method)
Use the Context7 MCP tools to fetch up-to-date documentation:
# First resolve the library ID
mcp__plugin_compound-engineering_context7__resolve-library-id({
query: "user's question or error",
libraryName: "expo" // or "react-native", "expo-router", etc.
})
# Then query the docs
mcp__plugin_compound-engineering_context7__query-docs({
libraryId: "/expo/expo", // from resolve step
query: "specific question about the issue"
})
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.
- 7d ago First seen · 180 lines · 35 tokens per session scan A 4b1528583089
expo-docs is an agent published in the GitHub repository rahulkeerthi/expo-toolkit (5 stars, last pushed 3mo ago), licensed MIT. It adds 35 tokens to every session and 1,226 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 agents, from other repositories
ux-flow-auditor
Use this agent when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app. Automatically scans SwiftUI and UIKit code for user journey defects - detects dead ends, dismiss traps, buried CTAs, missing loading/error/empty states…
android-performance-specialist
Specialist in Android app performance & diagnostics — app startup (cold/warm/hot, TTID/TTFD, App Startup lib), Baseline Profiles & Macrobenchmark, rendering/jank (frame budgets, slow/frozen frames, JankStats), ANRs (ApplicationExitInfo), memory (LeakCanary, LMK, onTrimMemory), Perfetto/Studio Profiler, Play Vitals…
swiftui-architect
Specialist in modern iOS app architecture with SwiftUI (iOS 26 / Swift 6.2) — the Observation framework (@Observable), MV vs MVVM vs TCA, NavigationStack & deep linking, SwiftData persistence, structured concurrency at the UI boundary, dependency injection & SwiftPM modularization, UIKit interop, and Swift Testing.…
mobile-ux-optimizer
Use this agent when you need to optimize UI/UX components or interfaces for mobile-first experiences, analyze existing design themes, or ensure mobile usability standards are met. Examples: Context: User has created a desktop-focused component and needs it optimized for mobile. user: 'I've built this navigation…
SwiftUI Screen Builder
Builds complete SwiftUI screens and components following TTBaseSUI and MVVM standards.
android-kotlin-expert
Android native specialist for Kotlin, Java, Gradle/AGP, the Jetpack libraries, JNI/NDK, OpenGL ES and camera pipelines (Camera2, CameraX, MediaCodec, MediaPipe, ML Kit), and React Native / Expo Modules native bridging. Use when the task touches android/ (.kt, .java, .gradle / .gradle.kts, AndroidManifest.xml…