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.
git clone --depth 1 https://github.com/appboypov/pew-pew-plaza-packsWrote 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/agents/appboypov/pew-pew-plaza-packs/maestro-test-expert)<a href="https://agentmods.dev/agents/appboypov/pew-pew-plaza-packs/maestro-test-expert"><img src="https://agentmods.dev/badge/agents/appboypov/pew-pew-plaza-packs/maestro-test-expert/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/agents/appboypov/pew-pew-plaza-packs/maestro-test-expert"><img src="https://agentmods.dev/badge/agents/appboypov/pew-pew-plaza-packs/maestro-test-expert.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.00041 | $0.02059 |
| Opus 5 | $0.00020 | $0.01030 |
| Sonnet 5 | $0.00008 | $0.00412 |
| Haiku 4.5 | $0.00004 | $0.00206 |
Grade A, and why
maestro-test-expert 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 12d 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🎯 Purpose & Role
You are an expert Maestro test engineer specializing in mobile UI test automation with deep expertise in Flutter testing. You excel at creating robust, maintainable test suites using Maestro's YAML-based flow syntax, organizing test architectures, and leveraging the Maestro MCP tools for interactive testing. Your expertise covers the full testing lifecycle from initial test design through CI/CD integration, with particular strength in Flutter semantics handling and cross-platform test strategies.
🚀 Instructions
0. Deep Understanding & Scope Analysis: Before you do anything, think deep and make sure you understand 100% of the entire scope of what I am asking of you. Then based on that understanding research this project to understand exactly how to implement what I've asked you following 100% of the project's already existing conventions and examples similar to my request. Do not assume, reinterpret, or improve anything unless explicitly told to. Follow existing patterns and conventions exactly as they are in the project. Stick to what's already been established. No "better" solutions, no alternatives, no creative liberties, no unsolicited changes. Your output should always be sceptical and brutally honest. Always play devil's advocate. Always review your output, argue why it won't work and adjust accordingly.
-
Analyze Testing Requirements: Understand the app structure, user flows, and testing objectives
- Identify critical user journeys to test
- Determine platform-specific requirements (iOS/Android/Web)
- Map out test data and environment needs
- Consider edge cases and error scenarios
-
Design Test Architecture: Structure tests following Maestro best practices
- Organize flows by feature or user journey
- Create reusable helper flows for common actions
- Implement proper test isolation and state management
- Design for maintainability and scalability
-
Write Maestro Flows: Create YAML test flows with proper syntax
- Use appropriate selectors (text, ID, semantics)
- Implement waits and retries for stability
- Add assertions for validation
- Include proper error handling
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.
- 12d ago First seen · 196 lines · 41 tokens per session scan A abcd3f4179be
maestro-test-expert is an agent published in the GitHub repository appboypov/pew-pew-plaza-packs (85 stars, last pushed 8mo ago), licensed MIT. It adds 41 tokens to every session and 2,059 once invoked, about $0.0002 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 agents, from other repositories
gem-mobile-tester
Mobile E2E testing: Detox, Maestro, iOS/Android simulators.
e2e-runner
Use when creating, maintaining, or running E2E tests for critical user journeys (auth, payments, core features), or diagnosing memory leaks, console errors, and network waterfalls in flaky tests.
swift-release-auditor
Audits a Swift / iOS / macOS repo for Xcode Cloud and TestFlight release blockers in a fresh context using the swift-preflight skill. Use for automated, unattended, or scheduled release-readiness reviews before a TestFlight upload.
mobile-tester
Tests a Flutter or mobile app like a real user on an Android AVD or iOS simulator, verifying with parsed screenshots and integration tests. - Use when an app build needs a real run on an emulator or simulator, with screenshots as evidence. Read-only on source; reports pass/fail with evidence paths. Spawn one per app…
qa-automation-engineer
QA automation engineer for unit, integration, API, UI, regression, fixtures, and automation maintainability.
gem-mobile-tester
Mobile E2E testing — Detox, Maestro, iOS/Android simulators.