Maestro is a testing framework for automating user-interface and end-to-end tests for Android, iOS, and web applications. Testers define interactions in human-readable YAML flows and run them on emulators, simulators, browsers, or real devices. The catalogue includes skills, instructions, and an agent for using Maestro.
Borrowing it
Nothing to install: this file belongs to mobile-dev-inc/Maestro. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mobile-dev-inc/Maestro/main/.claude/skills/bump-android-version/SKILL.mdgit clone --depth 1 https://github.com/mobile-dev-inc/MaestroWrote 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/mobile-dev-inc/maestro/bump-android-version)<a href="https://agentmods.dev/skills/mobile-dev-inc/maestro/bump-android-version"><img src="https://agentmods.dev/badge/skills/mobile-dev-inc/maestro/bump-android-version/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/mobile-dev-inc/maestro/bump-android-version"><img src="https://agentmods.dev/badge/skills/mobile-dev-inc/maestro/bump-android-version.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 146 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00046 | $0.02657 |
| Opus 5.5 | $0.00018 | $0.01063 |
| Sonnet 5.5 | $0.00009 | $0.00531 |
| Haiku 4.5 | $0.00005 | $0.00266 |
Grade A, and why
bump-android-version 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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bump Android Version
Overview
Drive an Android-version bump in Maestro commit-by-commit on a single feature branch: edit gradle, rebuild the on-device driver APKs, push a draft PR, dispatch test-e2e.yaml against the new system image, watch the test-android job, and diagnose+fix any newly-failing passing/ flows. Loop until green.
When to Use
- User asks to bump Maestro's Android
compileSdk/targetSdk(e.g. "bump to API 36"). - User wants to validate Maestro against a new Android system image.
One commit per logical step. Don't bundle the gradle bump and the APK rebuild — they need to be separately revertible. After a failing run, fixes are committed and the workflow re-dispatched. Loop until green; do not stop on the first re-dispatch.
The loop only acts on passing/ failures. tests/demo_app/passing/ is the regression-detection suite — its flows are expected to pass, so a failure there is a real signal. tests/demo_app/failing/ is the negative-path suite (its flows are expected to fail) and is ignored end-to-end. The diagnose agent rejects failing/ artifacts and rejects retry-recovered flows in passing/ (see .claude/agents/diagnose-maestro-failure.md). If the run is otherwise green except for failing/, that's a green run.
Pre-flight
- Working tree clean (
git status). mainup to date:git fetch origin && git checkout main && git pull --ff-only origin main.- The workflow's
workflow_dispatchinputsandroid_version(and optionalapp/flow) must exist on the branch. android_versionis achoiceinput — its options live in.github/workflows/test-e2e.yaml. If<new>isn't already listed (e.g. bumping to API 37), add it to theoptions:list in a separate commit before dispatching, otherwise the workflow rejects the input.- The
validate-inputsjob rejectsandroid_version <= android-29. Bumps below API 29 aren't supported. - Branch name:
bump-android-api-<old>-<new>(e.g.bump-android-api-34-36).
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 · 152 lines · 46 tokens per session scan A 032ea248b004
bump-android-version is a skill published in the GitHub repository mobile-dev-inc/Maestro (16,251 stars, last pushed yesterday), licensed Apache-2.0. It adds 46 tokens to every session and 2,657 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-08-30.
Other skills, from other repositories
argent-test-ui-flow
Autonomously test an app UI (iOS or Android) by running interact-screenshot-verify loops using argent MCP tools. Use when testing UI flows, verifying login works, testing navigation, running UI test scenarios, manual QA steps, visible UI changes, or visual behavior.
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.
argent-qa-e2e
Write repeatable QA regression e2e tests from test cases, tickets, or acceptance criteria. Use when the user asks to write, automate, or generate an e2e test or preserve an automated regression scenario, with deterministic setup, stable targets, executable structural or visual evidence, and two consecutive full…
argent-create-e2e
Create, record, edit, replay, or repair reusable Argent e2e test YAML files. Use when the user asks to record, replay, or run an e2e test or a repeatable device path, set up profiling or an A/B comparison, or invoke the authoring engine behind argent-qa-e2e. Also use before repeating three or more interactions. For…
mobilewright-cli
Automate iOS and Android apps on simulators, emulators and real devices, explore screens and write Mobilewright tests.
Appium Mobile Testing
Mobile application testing skill using Appium for iOS and Android, covering device capabilities, selectors, gestures, and cross-platform testing strategies.