What is device-inspector?

A local development-environment checker that lists available iOS simulators and Android emulators and checks whether fastlane and screenshot automation are ready. Simulators and emulators let developers run mobile apps without physical devices.

Use it to inspect device names, operating-system versions, identifiers, and running states, list Android virtual devices, check fastlane, and identify devices suitable for App Store screenshots.

It shows which virtual devices are available and whether the environment can support automated app screenshots before testing begins.

device-inspector — Agent for Claude Code by rahulkeerthi/expo-toolkit

Install

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.

Clone the repo

git clone --depth 1 https://github.com/rahulkeerthi/expo-toolkit

Made for: Claude Code.

Or install expo-toolkit, the plugin that ships this one along with the rest of its 6 skills, 7 commands, 5 agents.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/rahulkeerthi/expo-toolkit/device-inspector/github.svg)](https://agentmods.dev/agents/rahulkeerthi/expo-toolkit/device-inspector)

Your own site

<a href="https://agentmods.dev/agents/rahulkeerthi/expo-toolkit/device-inspector"><img src="https://agentmods.dev/badge/agents/rahulkeerthi/expo-toolkit/device-inspector/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.

Your own site · 80×15

<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="Reviewed on agentmods" width="80" height="20"></a>

Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,154 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.5	$0.00010	$0.00462
Sonnet 5.5	$0.00005	$0.00231
Haiku 4.5	$0.00002	$0.00115

Measured 2mo ago against content hash 13d8421a20d2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

agents/device-inspector.md · 205 lines

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" })

Read the full file on GitHub · 205 lines

Changes

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.

2mo ago First seen · 205 lines · 24 tokens per session scan A 13d8421a20d2

Subscribe to this mod's changes

device-inspector is an agent published in the GitHub repository rahulkeerthi/expo-toolkit (5 stars, last pushed 5mo ago), licensed MIT. It adds 24 tokens to every session and 1,154 once invoked, about $0.0001 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.

Mobile

device-inspector next to 6 agents from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
device-inspectorrahulkeerthi/expo-toolkit	Agent	5	5mo ago	MIT	A	24	Claude Code
ux-flow-auditorCharlesWiltgen/Axiom	Agent	1.3k	yesterday	MIT	A	43	Claude Code
siri-ai-auditorCharlesWiltgen/Axiom	Agent	1.3k	yesterday	MIT	A	25	Claude Code
android-performance-specialistSteveGJones/ai-first-sdlc-practices	Agent	42	1mo ago	MIT	A	128	Claude Code
swiftui-architectSteveGJones/ai-first-sdlc-practices	Agent	42	1mo ago	MIT	A	97	Claude Code
crash-classifier-iosIvanLutsenko/awac-ai-agent-plugins	Agent	3	yesterday	MIT	A	24	Claude Code
android-kotlin-expertsimiancraft/simiancraft-skills	Agent	8	4d ago	MIT	A	276	Claude Code