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.
npx skills add mttmcknn/android-emulator-plugin --skill setupgit clone --depth 1 https://github.com/mttmcknn/android-emulator-pluginWrote 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/skills/mttmcknn/android-emulator-plugin/setup)<a href="https://agentmods.dev/skills/mttmcknn/android-emulator-plugin/setup"><img src="https://agentmods.dev/badge/skills/mttmcknn/android-emulator-plugin/setup/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/skills/mttmcknn/android-emulator-plugin/setup"><img src="https://agentmods.dev/badge/skills/mttmcknn/android-emulator-plugin/setup.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.00039 | $0.00325 |
| Opus 5.5 | $0.00016 | $0.00130 |
| Sonnet 5.5 | $0.00008 | $0.00065 |
| Haiku 4.5 | $0.00004 | $0.00032 |
Grade A, and why
setup 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 today.
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.
What it actually says
Set Up Android Emulators
- Call
check_device_status.- If Platform Tools are missing, tell the user to install them with Android Studio or sdkmanager and set
ANDROID_HOMEif the SDK is in a custom location. Stop there. Physical devices do not need the emulator package.
- If Platform Tools are missing, tell the user to install them with Android Studio or sdkmanager and set
- If the status lists no AVDs, call
create_emulatorwithprofile: "pixel_9". If it reports that no system images are installed, tell the user to install one from Android Studio's SDK Manager, then stop. - Otherwise call
start_emulatorwith no arguments. - Successful startup opens the device panel automatically. Do not follow it with
show_device_panel; use that tool only to reopen a closed panel or when the user asks to show it. - Tell the user, briefly, where things are:
- The Android Emulator panel shows devices pinned to this chat. Use the dropdown to pin a connected phone or add another emulator. Compare or drag one device tab onto another for side-by-side testing.
- Android Emulators in the sidebar lists every running emulator and the devices on disk.
- Settings for the default device, idle shutdown, and video quality are on the plugin's page.
- Drag an APK onto the device to install it; the device controls list keyboard shortcuts.
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.
- today First seen · 18 lines · 39 tokens per session scan A f59239207725
setup is a skill published in the GitHub repository mttmcknn/android-emulator-plugin (17 stars, last pushed today), licensed Apache-2.0. It adds 39 tokens to every session and 325 once invoked, about $0.0002 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-10-18.
Other skills, from other repositories
android_ui_verification
Automated end-to-end UI testing and verification on an Android Emulator using ADB.
solopi-ai
A command-line framework for testing Android apps and devices with SoloPi, including on-device or cloud AI decision models. It manages devices, test cases, recorded interactions, replays, performance history, and evidence.
ios-simulator
Verify and debug native, React Native, Expo, or Flutter apps on an iOS Simulator with agent-device. Use when an agent needs to launch an app, inspect its live UI, tap, type, scroll, validate a code change, collect failure evidence, or reproduce a workflow on an iPhone or iPad Simulator.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
eas-simulator
Run and control a user's app on a remote iOS/Android simulator hosted on EAS cloud. Read before running any eas simulator: commands - it has the current syntax for this experimental API. Use whenever the user needs a simulator they can't run locally - 'run my app on a cloud simulator', 'use eas simulator to…
mobile-automation
Control Android and iOS devices, emulators and simulators — launch apps, tap, swipe, type, take screenshots, read the accessibility tree. Use when a task involves a mobile device or app, mobile UI testing, or reproducing a bug on a phone.