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 iurysza/android-use --skill android-usegit clone --depth 1 https://github.com/iurysza/android-useWrote 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/iurysza/android-use/android-use)<a href="https://agentmods.dev/skills/iurysza/android-use/android-use"><img src="https://agentmods.dev/badge/skills/iurysza/android-use/android-use/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/iurysza/android-use/android-use"><img src="https://agentmods.dev/badge/skills/iurysza/android-use/android-use.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.00033 | $0.02911 |
| Opus 5.5 | $0.00013 | $0.01164 |
| Sonnet 5.5 | $0.00007 | $0.00582 |
| Haiku 4.5 | $0.00003 | $0.00291 |
Grade C, and why
android-use scanned grade C with 2 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 1mo 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -fsSL https://raw.githubusercontent.com/iurysza/android-use/main/install.sh | bash Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsSL https://raw.githubusercontent.com/iurysza/android-use/main/install.sh | bash How it starts
The opening of the file, as written. The whole thing — 362 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Android Device Control
CLI for Android device control via ADB. Requires device connected with USB debugging enabled.
Prerequisites
Before using this skill:
- Android device with USB debugging enabled
- ADB installed (
adb versionshould work) - Device connected via USB or emulator running
Agent Installation (Autonomous Setup)
When this skill is not installed, agents should:
-
Run installer (recommended):
curl -fsSL https://raw.githubusercontent.com/iurysza/android-use/main/install.sh | bash -
Installed structure:
~/.config/opencode/skill/android-use/SKILL.md~/.config/opencode/skill/android-use/scripts/android-use~/.config/opencode/skill/android-use/references/~/.config/opencode/skill/android-use/assets/~/.config/opencode/skill/android-use/repo/
-
Verify installation:
~/.config/opencode/skill/android-use/scripts/android-use check-device
Quick Start
android-use check-device # List connected devices
android-use get-screen # Get UI hierarchy (compact JSON)
android-use tap 540 960 # Tap at coordinates
android-use type-text "Hello" # Type text
android-use key HOME # Press key
android-use screenshot ./screen.png # Capture screen
Core Agent Workflow
STEP 1: Check device
android-use check-device
- Lists all connected devices
- Note the serial number if multiple devices
- For "phone" use [PHYSICAL] device
- For "emulator" use [EMULATOR] device
STEP 2: Get screen state
android-use get-screen
- Returns compact JSON with pre-calculated tap coordinates
- Search for:
text,contentDesc,resourceId - Use the
centerfield for coordinates (e.g.,"center": [540, 289]) - Cache location:
/tmp/.ai-artifacts/skills/android-use/screen.json
STEP 3: Execute action
- Tap:
android-use tap <center_x> <center_y> - Type:
android-use tap <field_x> <field_y>thenandroid-use type-text "text" - Swipe:
android-use swipe <x1> <y1> <x2> <y2> [duration_ms] - Key:
android-use key <KEY_NAME>(HOME, BACK, ENTER, etc.)
What ships with it
9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- assets/logo-banner.png 27 KB
- references/01-taking-a-screenshot.md 1.1 KB
- references/02-opening-an-app.md 1.6 KB
- references/03-tapping-a-button.md 2.0 KB
- references/04-filling-a-form.md 2.5 KB
- references/05-scrolling-to-find-content.md 2.9 KB
- references/06-handling-dialogs.md 3.0 KB
- references/AGENT_WORKFLOWS.md 3.3 KB
- references/AGENTS_GETTING_STARTED.md 6.3 KB
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.
- 1mo ago First seen · 362 lines · 33 tokens per session scan C f67ef37d3311
android-use is a skill published in the GitHub repository iurysza/android-use (21 stars, last pushed 16d ago), licensed MIT. It adds 33 tokens to every session and 2,911 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
agent-device
Automates Apple-platform apps (iOS, tvOS, macOS), Android devices, and Amazon Vega OS TV apps in Vega Virtual Devices. Use when navigating apps, taking snapshots/screenshots where supported, driving TV remotes, tapping, typing, scrolling, extracting UI info, collecting evidence, or planning agent-device CLI commands.
android-emulator
Verify and debug native, React Native, Expo, or Flutter apps on an Android Emulator 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 Android virtual device.
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.
phone-harness
Use when an agent needs to control a real phone — iPhone via Mac iPhone Mirroring or Android via adb (open apps, tap, type, swipe, OCR the screen). Android path runs on this Linux workstation (adb), targets phonefarm devices. iOS path needs macOS + iPhone Mirroring. Use for phonefarm device debugging, OTP/2FA flows…
android-ui-journey-testing
XML-specified Android UI journey testing, interactive step execution, assertion verification, and JSON outcome reporting.