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-fix-cyclegit 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-fix-cycle)<a href="https://agentmods.dev/skills/parisgroup-ai/imersao-ia-setup/maestro-fix-cycle"><img src="https://agentmods.dev/badge/skills/parisgroup-ai/imersao-ia-setup/maestro-fix-cycle/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-fix-cycle"><img src="https://agentmods.dev/badge/skills/parisgroup-ai/imersao-ia-setup/maestro-fix-cycle.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.00073 | $0.03825 |
| Opus 5 | $0.00036 | $0.01912 |
| Sonnet 5 | $0.00015 | $0.00765 |
| Haiku 4.5 | $0.00007 | $0.00382 |
Grade A, and why
maestro-fix-cycle 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.
How it starts
The opening of the file, as written. The whole thing — 466 lines — stays where its author put it; the contents beside it link to each section on GitHub.
maestro-fix-cycle - Flow-by-Flow Test-Fix Loop with Memory
Processes Maestro flows one at a time, maintaining state across sessions. Analyzes failures, fixes YAML flows or app code, and re-runs until all pass.
Usage
/maestro-fix-cycle # Start/continue cycle
/maestro-fix-cycle auth # Only auth flows
/maestro-fix-cycle student # Only student flows
/maestro-fix-cycle continue # Resume from last position
/maestro-fix-cycle reset # Clear memory and start fresh
/maestro-fix-cycle status # Show current progress
/maestro-fix-cycle studio # Debug current flow in Maestro Studio
Memory System
State persisted in apps/mobile/.maestro-cycle/:
.maestro-cycle/
├── state.json # Current position, queued flows
├── history.jsonl # All fixes applied (append-only)
├── learnings.md # Patterns discovered (human-readable)
└── failures/ # Detailed failure logs per flow
└── {flow-name}.json
state.json
{
"version": "1.0",
"started_at": "2026-03-01T18:00:00Z",
"updated_at": "2026-03-01T18:45:00Z",
"current_flow": "flows/auth/login.yaml",
"current_iteration": 1,
"queue": [
"flows/auth/token-refresh.yaml",
"flows/student/courses-pagination.yaml"
],
"completed": [
"flows/smoke/smoke.yaml"
],
"failed_permanently": [],
"total_fixes": 3,
"session_id": "abc123"
}
learnings.md
# Maestro Fix Learnings
> Auto-updated by maestro-fix-cycle. Manual edits welcome.
## Known Patterns
### Pattern: text-mismatch
- **Symptoms:** tapOn/assertVisible fails — element not found by text
- **Cause:** Button/label text in app differs from flow YAML
- **Solution:** Update text in YAML, or migrate to testID
- **How to find correct text:** Check component source or use `maestro studio`
### Pattern: locale-mismatch
- **Symptoms:** English text assertion fails on pt-BR simulator
- **Cause:** Simulator locale differs from flow expectations
- **Solution:** Use testID selectors (locale-independent)
- **Files seen:** All flows using text-based selectors
### Pattern: animation-timing
- **Symptoms:** Step fails intermittently after navigation
- **Cause:** waitForAnimationToEnd resolves before render completes
- **Solution:** Add explicit assertVisible for target element after wait
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 · 466 lines · 73 tokens per session scan A 58c804f7a5b0
maestro-fix-cycle is a skill published in the GitHub repository parisgroup-ai/imersao-ia-setup (1 stars, last pushed 29d ago), licensed MIT. It adds 73 tokens to every session and 3,825 once invoked, about $0.0004 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.