android-emulator

A guide for checking native, React Native, Expo, and Flutter apps on an Android Emulator, a virtual Android device. It uses agent-device to launch apps, inspect screens, interact with controls, and collect evidence of failures.

In plain words
What is it for?
Use it to open an app, tap and type through workflows, scroll, inspect the interface, validate changes, reproduce bugs, and gather screenshots or other failure evidence.
Why use it?
It lets an agent verify how an app behaves on Android instead of relying only on source-code inspection. This helps reproduce user flows and confirm whether a change works on a live device.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/callstack/agent-device/android-emulator
Any agent
npx skills add callstack/agent-device --skill android-emulator
Clone the repo
git clone --depth 1 https://github.com/callstack/agent-device

Made for: Claude Code, Codex.

Per session 65 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 346 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00065 $0.00346
Opus 5 $0.00032 $0.00173
Sonnet 5 $0.00013 $0.00069
Haiku 4.5 $0.00006 $0.00035

Measured 2d ago against content hash eab18adf3b0b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

android-emulator 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 2d 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.

skills/android-emulator/SKILL.md · 33 lines

What it actually says

Android Emulator

Require the agent-device CLI to be installed separately before driving an emulator:

npm install -g agent-device@latest

Treat installation and upgrades as user-owned setup steps. Do not run that command autonomously or substitute a mutable npx -y agent-device@latest invocation.

For a normal app-driving task, start immediately. Do not probe first with --help, --version, devices, appstate, snapshot, or screenshot. Target Android explicitly when opening an app or package id:

agent-device open <app-or-package-id> --platform android --foreground

Follow the initial interactive snapshot and corrective error hints. If the shell reports that agent-device is unavailable, stop and ask the user to install it or expose their existing installation on PATH.

Only when the task is specialized or a command shape is unclear, read the relevant version-matched help topic:

agent-device help validate        # engineering validation and build freshness
agent-device help debugging       # screenshots, logs, traces, video, and failures
agent-device help react-native    # React Native and Expo runtime guidance
agent-device help react-devtools  # component tree, props/state/hooks, and renders
agent-device help scripting       # durable replay and CI workflows
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.

  1. 2d ago First seen · 33 lines · 65 tokens per session scan A eab18adf3b0b

Subscribe to this mod's changes

android-emulator is a skill published in the GitHub repository callstack/agent-device (4,300 stars, last pushed yesterday), licensed MIT. It adds 65 tokens to every session and 346 once invoked, about $0.0003 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-30.