maestro-capture

maestro-capture is a skill for Claude Code from parisgroup-ai/imersao-ia-setup. It costs 63 tokens per session (567 once invoked), scanned A, original, MIT.

A tool for capturing screens from an iOS Simulator after navigating through a mobile app with Maestro flows. It can also compare the captured screen with a prototype image.

In plain words
What is it for?
Use it to capture a named app section, navigate through Expo Go when needed, and compare the result with a design reference.
Why use it?
It makes it easier to check whether the running app matches the intended mobile design. It also detects basic setup problems, such as a simulator or app that is not ready.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the imersao plugin — 51 skills, 7 commands shipped together

Good fit Use it to capture a named app section, navigate through Expo Go when needed, and compare the result with a design reference.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/parisgroup-ai/imersao-ia-setup/maestro-capture
Install

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.

Any agent
npx skills add parisgroup-ai/imersao-ia-setup --skill maestro-capture
Clone the repo
git clone --depth 1 https://github.com/parisgroup-ai/imersao-ia-setup

Made for: Claude Code.

Or install imersao, the plugin that ships this one along with the rest of its 51 skills, 7 commands.

Wrote 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.

agentmods badge for maestro-capture

README.md
[![agentmods](https://agentmods.dev/badge/skills/parisgroup-ai/imersao-ia-setup/maestro-capture/github.svg)](https://agentmods.dev/skills/parisgroup-ai/imersao-ia-setup/maestro-capture)
Your own site
<a href="https://agentmods.dev/skills/parisgroup-ai/imersao-ia-setup/maestro-capture"><img src="https://agentmods.dev/badge/skills/parisgroup-ai/imersao-ia-setup/maestro-capture/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.

agentmods 80×15 button for maestro-capture

Your own site · 80×15
<a href="https://agentmods.dev/skills/parisgroup-ai/imersao-ia-setup/maestro-capture"><img src="https://agentmods.dev/badge/skills/parisgroup-ai/imersao-ia-setup/maestro-capture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 567 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00063 $0.00567
Opus 5 $0.00032 $0.00283
Sonnet 5 $0.00013 $0.00113
Haiku 4.5 $0.00006 $0.00057

Measured 11d ago against content hash 03b424639c95, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

maestro-capture 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 11d 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.

plugins/imersao/skills/maestro-capture/SKILL.md · 65 lines

What it actually says

Maestro Capture

Capture screenshots from the iOS Simulator after navigating via Maestro flows, then compare with design prototypes.

Usage

/maestro-capture <section> [--compare]
  • section: Screen name to capture (e.g., settings, launch, inbox)
  • --compare: Also read the prototype PNG and show side-by-side analysis

Steps

  1. Check simulator is booted:

    xcrun simctl list devices booted
    

    If no device is booted, tell the user to start the simulator.

  2. Check if app is running: Take a quick screenshot to see the current state.

    xcrun simctl io booted screenshot /tmp/maestro-capture-check.png
    

    Read the screenshot to determine if the app is on screen or if Expo Go home is showing.

  3. Navigate to the target screen:

    • If on Expo Go home: create a temp Maestro YAML to tap "AsyncMe Mobile" and navigate
    • Write a temp YAML flow at /tmp/maestro-capture-nav.yaml that:
      • Launches host.exp.Exponent
      • Taps into the app if needed
      • Navigates to the target screen via bottom tab
    • Run: maestro test /tmp/maestro-capture-nav.yaml
  4. Capture screenshot:

    xcrun simctl io booted screenshot <project-root>/compare-<section>.png
    
  5. Read and display the captured screenshot using the Read tool.

  6. If --compare flag:

    • Look for prototype at design/sections/<section>/<section>-view-native.png
    • Read both images
    • Provide a structured gap analysis:
      • Layout differences
      • Missing elements
      • Style mismatches
      • What's aligned

Notes

  • Always use host.exp.Exponent as the Maestro appId (Expo Go)
  • Bottom tab labels are in English: Launch, Inbox, Processes, Projects, Settings
  • Inner content uses the device locale (Portuguese on PT devices)
  • Maestro tapOn works with visible text labels
  • For scrolling to off-screen elements use scrollUntilVisible
  • Clean up temp YAML files after use
Changes

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.

  1. 11d ago First seen · 65 lines · 63 tokens per session scan A 03b424639c95

Subscribe to this mod's changes

maestro-capture is a skill published in the GitHub repository parisgroup-ai/imersao-ia-setup (1 stars, last pushed 29d ago), licensed MIT. It adds 63 tokens to every session and 567 once invoked, about $0.0003 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-31.

Related

Other skills, from other repositories

test-native-extension

Validate a third-party control repo across four automated layers plus one printed manual recipe. Layer 1 asserts native-source structure (Android getName() and iOS +moduleName to manifest nativeModule; @ReactMethod / RCTEXPORTMETHOD to methods; no @ReactModule) plus load/init readiness (ReactPackage public no-arg…

microsoft/power-platform-skills · 211 tokens

asc-shots-pipeline

Orchestrate iOS screenshot automation with xcodebuild/simctl for build-run, AXe for UI actions, JSON settings and plan files, Koubou-based framing (asc screenshots frame), and screenshot upload (asc screenshots upload). Use when users ask for automated screenshot capture, AXe-driven simulator flows, frame composition…

rorkai/app-store-connect-cli-skills · 79 tokens

mobile-testing-detox

Detox E2E gray-box testing for React Native - matchers, actions, expectations, waitFor, device API, synchronization, mocking, artifacts, CI integration.

agents-inc/skills · 38 tokens

mobile-testing-maestro

Maestro mobile E2E testing - YAML flows, selectors, flow control, environment variables, JavaScript expressions, device interactions, Maestro Studio, Maestro Cloud CI, tags, test suites.

agents-inc/skills · 42 tokens

ios-device-qa

Use when the user runs /ios-device-qa to drive a real iPhone over USB through a debug-bridge daemon and return a device QA report with verified interactions. Do not use for remote, credential, publish, deploy, or irreversible changes.

OutlineDriven/odin-claude-plugin · 55 tokens

xcode-simulator-testing

Use when asked to run /xcode-simulator-testing with a scheme name or current to build and launch an iOS app in a simulator. Not for project regeneration: use ios-build-fix.

OutlineDriven/odin-claude-plugin · 46 tokens