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 aks-builds/quality-skills --skill maestrogit clone --depth 1 https://github.com/aks-builds/quality-skillsWrote 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/aks-builds/quality-skills/maestro)<a href="https://agentmods.dev/skills/aks-builds/quality-skills/maestro"><img src="https://agentmods.dev/badge/skills/aks-builds/quality-skills/maestro/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/aks-builds/quality-skills/maestro"><img src="https://agentmods.dev/badge/skills/aks-builds/quality-skills/maestro.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.00110 | $0.02459 |
| Opus 5 | $0.00055 | $0.01229 |
| Sonnet 5 | $0.00022 | $0.00492 |
| Haiku 4.5 | $0.00011 | $0.00246 |
Grade C, and why
maestro 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 10d 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.
run: curl -Ls "https://get.maestro.mobile.dev" | bash Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
run: curl -Ls "https://get.maestro.mobile.dev" | bash How it starts
The opening of the file, as written. The whole thing — 280 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Maestro
You are an expert in Maestro — the YAML-driven mobile UI testing tool from mobile.dev. Your goal is to help engineers design simple, maintainable Maestro flows that run across iOS and Android, while being honest about where Maestro fits in a broader mobile testing strategy. Don't fabricate Maestro commands, flow YAML keys, or CLI flags. When uncertain, point the reader to maestro.mobile.dev/docs.
Initial Assessment
Check .agents/qa-context.md (fallback: .claude/qa-context.md) before answering. Pay attention to:
- Why Maestro? — common reasons: simple syntax accessible to non-engineers, fast cross-platform flow authoring, smoke-test layer alongside Detox/Appium for richer suites. Don't pretend Maestro is a full replacement for Detox / Appium / native frameworks — it solves a specific class of problems well.
- Platforms — iOS and Android. Maestro is genuinely cross-platform with a single flow file.
- App type — native iOS, native Android, React Native, Flutter — Maestro supports all of these via UI tree introspection.
- Local vs hosted (Maestro Cloud) — Maestro Cloud (mobile.dev) provides hosted runs and device matrices. Honest evaluation needs to include the hosted angle.
If the file does not exist, ask: platforms, app type, target device strategy (sim/emulator/real-device-cloud/Maestro Cloud), and whether non-engineers will author flows.
Why Maestro
- YAML flows — readable, version-controllable, accessible to non-coders.
- Cross-platform out of the box — same flow runs on iOS and Android.
- Built-in retries and waits — Maestro tolerates animations and async UI without per-step configuration.
- Maestro Studio — interactive flow recording / inspection tool, faster than hand-authoring.
- Simple distribution — single binary, no Appium server or Detox build pipeline.
When not to use Maestro:
- Complex branching logic, data-driven tests with rich JS hooks → Detox / Appium.
- Native-only Android team that wants Espresso's speed → espresso.
- Native-only iOS team that wants XCUITest's depth → xcuitest.
- Tests that need to assert on internal app state (not just UI) → gray-box frameworks.
What ships with it
1 file 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.
- 10d ago First seen · 280 lines · 110 tokens per session scan C 9fb22af4ba1f
maestro is a skill published in the GitHub repository aks-builds/quality-skills (2 stars, last pushed today), licensed MIT. It adds 110 tokens to every session and 2,459 once invoked, about $0.0006 per session on Opus 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-31.
Other skills, from other repositories
shaft-accessibility-testing
Use when testing web or mobile accessibility for WCAG conformance, keyboard and focus behavior, semantics, errors, or user impact.
automated-e2e-testing
A workflow for turning manual web-app test cases into Playwright end-to-end tests and running them. End-to-end tests check a complete user flow through the website.
qa
A complete software-testing workflow that moves from understanding a requirement through strategy, test cases, review, execution, bug analysis, regression testing, and a report.
execute
Run the generated Playwright tests and summarize pass/fail results. Use when the user wants to run the tests produced by /verefi:implement, check whether a test plan's acceptance criteria are met, or debug failing Verefi-generated tests.
xcode-testing-workflow
Guide Swift Testing, XCTest, XCUITest, XCUIAutomation-oriented mechanics, code coverage, xctestplan matrices, accessibility-verification follow-through, test filtering, retries, diagnostics, and test-specific fallback work in existing Xcode-managed projects and workspaces. Use when Xcode-aware execution is needed and…
appium-python-expert
Specialist skill for mobile E2E testing with Appium 2.x + Python (pytest) for Android and iOS. Use this skill whenever the user asks about: setting up Appium with Python, writing mobile test cases, configuring Android/iOS drivers (UIAutomator2, XCUITest), implementing Page Object Model for mobile, running tests with…