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 instructions/mobile-dev-inc/maestro/agents-mdgit clone --depth 1 https://github.com/mobile-dev-inc/MaestroWhat 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 | $0.03171 | $0.03171 |
| Opus 5 | $0.01586 | $0.01586 |
| Sonnet 5 | $0.00634 | $0.00634 |
| Haiku 4.5 | $0.00317 | $0.00317 |
Grade A, and why
Maestro AGENTS.md 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 2d 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — Maestro
Shared context for any Claude Code skill or subagent operating in this repo. Skills (.claude/skills/*) reference this file rather than restating module roles; if a description here drifts from reality, fix it here once and every skill follows.
Module map
Top-level Gradle modules. Code lives under each module's src/main/.
| Module | Role |
|---|---|
maestro-android/ |
On-device Android driver. Kotlin sources compile to two checked-in APKs (maestro-app.apk, maestro-server.apk) consumed by maestro-client/. The build's copyMaestroAndroid / copyMaestroServer finalizers update those APKs plus a maestro-android-source.sha256 checksum. |
maestro-ios-driver/ |
Host side of iOS driver wrapper (Kotlin). The actual XCTest runner lives in maestro-ios-xctest-runner/. |
maestro-ios-xctest-runner/ |
Swift XCTest runner that runs on the iOS device/simulator. The compiled artifacts (maestro-driver-ios*.zip) are checked in under maestro-ios-driver/src/main/resources/driver-iPhoneSimulator/Debug-iphonesimulator/. |
maestro-ios/ |
iOS host-side glue (small — most iOS host code lives in maestro-client/). |
maestro-client/ |
Host-side Kotlin SDK that drives devices. Platform drivers live in src/main/java/maestro/drivers/: AndroidDriver.kt, IOSDriver.kt, WebDriver.kt, CdpWebDriver.kt. This is where most "auto-grant", "auto-dismiss", system-dialog handling and platform-specific quirks belong. |
maestro-orchestra/ |
Command execution layer. Orchestra.kt interprets each Maestro command, applies retries, manages the command lifecycle. Sub-packages: error/, filter/, workspace/, yaml/. |
maestro-orchestra-models/ |
Shared command/data models (used by maestro-orchestra/ and consumers). |
maestro-cli/ |
CLI entry point + MCP server. Mixed Kotlin (~100 files) + Swift (~56 files for iOS-related CLI bits). |
maestro-utils/ |
Shared utilities. |
maestro-web/ |
Web (browser) driver pieces. |
maestro-proto/ |
Protobuf definitions shared across modules. |
maestro-test/ |
Cross-module tests that doesn't require devices. |
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.
- 2d ago First seen · 135 lines · 3,171 tokens per session scan A 6156767260be
Maestro AGENTS.md is an instructions file published in the GitHub repository mobile-dev-inc/Maestro (15,456 stars, last pushed 4d ago), licensed Apache-2.0. It adds 3,171 tokens to every session, about $0.0159 per session on Opus 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 instructions, from other repositories
react-native-restart CLAUDE.md
Instructions for avishayil/react-native-restart, covering claude.md, what this is, architecture, repository map and common commands.
tapflow AGENTS.md
AGENTS.md instructions for jo-duchan/tapflow, covering tapflow — agents.md (common rules), what, core value, two testing modes and why.
maui-labs devflow-architecture.instructions.md
Instructions for dotnet/maui-labs, covering devflow architecture, communication model, package dependency graph, the abstractions / backend split and key extension points.
AppClaw CLAUDE.md
Instructions for appclawhq/AppClaw, covering claude.md, what is appclaw?, build & run commands, architecture and entry point & cli modes (src/index.ts).
ios-simulator-skill CLAUDE.md
Instructions for conorluddy/ios-simulator-skill, covering claude.md - developer guide, project overview, project structure, architecture patterns and pattern 1: class-based script design.
mobile-observability CLAUDE.md
Instructions for nexus-labs-automation/mobile-observability, covering mobile observability plugin, project context, plugin components, key commands and skills.