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 parisgroup-ai/imersao-ia-setup --skill maestro-capturegit clone --depth 1 https://github.com/parisgroup-ai/imersao-ia-setupWrote 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/parisgroup-ai/imersao-ia-setup/maestro-capture)<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.
<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>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.00063 | $0.00567 |
| Opus 5 | $0.00032 | $0.00283 |
| Sonnet 5 | $0.00013 | $0.00113 |
| Haiku 4.5 | $0.00006 | $0.00057 |
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.
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
-
Check simulator is booted:
xcrun simctl list devices bootedIf no device is booted, tell the user to start the simulator.
-
Check if app is running: Take a quick screenshot to see the current state.
xcrun simctl io booted screenshot /tmp/maestro-capture-check.pngRead the screenshot to determine if the app is on screen or if Expo Go home is showing.
-
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.yamlthat:- Launches
host.exp.Exponent - Taps into the app if needed
- Navigates to the target screen via bottom tab
- Launches
- Run:
maestro test /tmp/maestro-capture-nav.yaml
-
Capture screenshot:
xcrun simctl io booted screenshot <project-root>/compare-<section>.png -
Read and display the captured screenshot using the Read tool.
-
If
--compareflag:- 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
- Look for prototype at
Notes
- Always use
host.exp.Exponentas 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
tapOnworks with visible text labels - For scrolling to off-screen elements use
scrollUntilVisible - Clean up temp YAML files after use
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.
- 11d ago First seen · 65 lines · 63 tokens per session scan A 03b424639c95
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.
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…
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…
mobile-testing-detox
Detox E2E gray-box testing for React Native - matchers, actions, expectations, waitFor, device API, synchronization, mocking, artifacts, CI integration.
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.
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.
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.