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 agentmods add skills/aivanelabs/ai-rpa/agent-androidnpx skills add aivanelabs/ai-rpa --skill agent-androidgit clone --depth 1 https://github.com/aivanelabs/ai-rpaWrote 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/aivanelabs/ai-rpa/agent-android)<a href="https://agentmods.dev/skills/aivanelabs/ai-rpa/agent-android"><img src="https://agentmods.dev/badge/skills/aivanelabs/ai-rpa/agent-android.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.00017 | $0.02632 |
| Opus 5 | $0.00009 | $0.01316 |
| Sonnet 5 | $0.00003 | $0.00526 |
| Haiku 4.5 | $0.00002 | $0.00263 |
Grade A, and why
agent-android scanned grade A with 1 finding 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 6d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Re-open the app or restart the phone-side service, then retry `curl http://<device-ip>:8080/health`. How it starts
The opening of the file, as written. The whole thing — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Android REPL
Use this skill to drive an Android device through the public agent-android beta surface published in the aivanelabs/ai-rpa repo.
Runtime prerequisites:
agent-androidis available onPATH- if it is missing, install the CLI with
uv tool install aivane-agent-android; then runuv tool update-shellif the command is still not found - the user has provided a trusted device URL such as
http://<device-ip>:8080; use the phone-side configured port if it is not8080
The public path is local-first:
- the phone hosts the lightweight HTTP service locally
- the desktop connects directly to the phone URL, usually
http://<device-ip>:8080 - UI reads, taps, inputs, and screenshots stay on the phone and controlling machine
- the current tradeoff is LAN-only control; an optional server-side or relay path may arrive later
If an agent-android command suddenly stops working, first check whether the AIVane app or its local API service has exited on the phone.
Safety Boundaries
- Connect only to a device URL explicitly provided by the user.
- Do not scan local networks or guess device IP addresses.
- Treat UI trees and screenshots as sensitive because they may contain private app content.
- Save screenshots or raw UI dumps only when the user explicitly asks for a file output.
- Ask for confirmation before operating sensitive apps, private content, account settings, or irreversible actions.
- Do not expose the phone-side service on a public network.
Core Workflow
Every Android control task should follow the same short loop:
- Confirm connectivity with
/health - Discover the target app with
appsif needed - Launch one app
- Inspect the current UI tree
- Perform one action
- Inspect again
Keep the loop short. Prefer inspect -> act -> inspect over long speculative command chains.
Quick Start
Start the REPL with the user-provided device URL:
agent-android --repl --url http://<device-ip>:8080
Built-in help:
agent-android --help- In the REPL:
h
What ships with it
2 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.
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.
- 6d ago First seen · 244 lines · 17 tokens per session scan A 556e5f8d27a5
agent-android is a skill published in the GitHub repository aivanelabs/ai-rpa (11 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 2,632 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (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
autofish-control
Control Android devices with Autofish via the af CLI. Use this skill when you need reliable observe-act-verify loops, ref-based tapping, overlay management, screenshots, and recovery steps.
open-gui-remote-control
Control an Android phone through OpenGUI from an AI coding agent such as Claude Code, Codex, or OpenCode. Use when an agent should list online devices, run a natural-language mobile task, check execution status, pause, resume, or cancel through the local OpenGUI backend and CLI.
open-gui-bootstrap
Launch and bootstrap OpenGUI from a plain-language user request. Use when an AI coding agent such as Claude Code, Codex, or OpenCode should install, configure, debug, and run the backend and Android client shipped in this repository while keeping manual setup to a minimum.
control
Automatically control locally connected Android phones with OpenGUI screenshots and allowlisted actions whenever a request targets a phone, Android app, mobile game, or multiple devices. The user does not need to name OpenGUI. Use the native Codex Browser instead for browser-only work.
mobilerun-docs
Mobilerun documentation reference. Use when users ask about Mobilerun setup, configuration, SDK usage, CLI commands, device setup, agents, architecture, app cards, credentials, tracing, Docker, migration, structured output, or any Mobilerun "how do I..." questions.
sim-use
Drive iOS Simulator, Android emulator/device, and physical iPhone/iPad screens for AI agents. Use when asked to automate a simulator or emulator, drive a real iOS device, tap/swipe/type on a device, describe UI, take a screenshot, or interact with a mobile app.