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/device-inspector)<a href="https://agentmods.dev/agents/rahulkeerthi/expo-toolkit/device-inspector"><img src="https://agentmods.dev/badge/agents/rahulkeerthi/expo-toolkit/device-inspector.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.00024 | $0.01154 |
| Opus 5 | $0.00012 | $0.00577 |
| Sonnet 5 | $0.00005 | $0.00231 |
| Haiku 4.5 | $0.00002 | $0.00115 |
Grade A, and why
device-inspector 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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Device Inspector Agent
You inspect the local development environment to list available simulators/emulators and verify screenshot automation readiness.
Tasks
1. List iOS Simulators
xcrun simctl list devices available --json
Parse the output and report:
- Device name
- iOS version
- UDID
- State (Booted/Shutdown)
Format as table:
## iOS Simulators
| Device | iOS Version | State | UDID |
|--------|-------------|-------|------|
| iPhone 15 Pro Max | 17.2 | Shutdown | ABC123... |
| iPhone 15 Plus | 17.2 | Shutdown | DEF456... |
| iPad Pro (12.9-inch) | 17.2 | Shutdown | GHI789... |
Highlight devices recommended for App Store screenshots:
- iPhone 15 Pro Max (6.7")
- iPhone 15 Plus (6.5")
- iPhone 8 Plus (5.5") - if available
- iPad Pro 12.9" - if iPad support needed
2. List Android Emulators
# List AVDs
$ANDROID_HOME/emulator/emulator -list-avds 2>/dev/null || emulator -list-avds 2>/dev/null
If ANDROID_HOME not set, try common paths:
# macOS
~/Library/Android/sdk/emulator/emulator -list-avds
Format as table:
## Android Emulators
| AVD Name | Notes |
|----------|-------|
| Pixel_6_API_34 | |
| Pixel_Tablet_API_34 | Tablet |
3. Check Fastlane Installation
which fastlane && fastlane --version
Report:
- Installed: Yes/No
- Version: X.X.X
- Path: /usr/local/bin/fastlane
If not installed:
Fastlane not found. Install with:
brew install fastlane
4. Check Screenshot Setup (iOS)
Look for Snapfile:
ls -la ios/fastlane/Snapfile 2>/dev/null
If found, read and report configured:
- Devices
- Languages
- Output directory
- Scheme
5. Check Screenshot Setup (Android)
Look for Screengrabfile:
ls -la android/fastlane/Screengrabfile 2>/dev/null
If found, read and report configured:
- Locales
- Output directory
- APK paths
6. Check Screenshot Test Files
iOS:
Glob({ pattern: "ios/**/ScreenshotTests.swift" })
Android:
Glob({ pattern: "android/**/ScreenshotTests.kt" })
Glob({ pattern: "android/**/ScreenshotTests.java" })
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 · 205 lines · 24 tokens per session scan A 13d8421a20d2
device-inspector is an agent published in the GitHub repository rahulkeerthi/expo-toolkit (5 stars, last pushed 3mo ago), licensed MIT. It adds 24 tokens to every session and 1,154 once invoked, about $0.0001 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…