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/commands/appboypov/pew-pew-plaza-packs/maestro-selectors-best-practices)<a href="https://agentmods.dev/commands/appboypov/pew-pew-plaza-packs/maestro-selectors-best-practices"><img src="https://agentmods.dev/badge/commands/appboypov/pew-pew-plaza-packs/maestro-selectors-best-practices/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/commands/appboypov/pew-pew-plaza-packs/maestro-selectors-best-practices"><img src="https://agentmods.dev/badge/commands/appboypov/pew-pew-plaza-packs/maestro-selectors-best-practices.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.00019 | $0.01791 |
| Opus 5 | $0.00010 | $0.00896 |
| Sonnet 5 | $0.00004 | $0.00358 |
| Haiku 4.5 | $0.00002 | $0.00179 |
Grade A, and why
maestro-selectors-instructions 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 9d 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 — 366 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Instruction Command
When this command is used, acknowledge that you understand these instructions and will follow them throughout the conversation. Then await the user's request.
🎯 Maestro Selectors Guide
💡 Comprehensive guide to targeting UI elements effectively in Maestro tests.
Selector Types
Basic Selectors
# Text selector (shorthand)
- tapOn: "Button Text"
# Text selector (explicit)
- tapOn:
text: "Button Text"
# ID selector
- tapOn:
id: "submit_button"
# Index selector (0-based)
- tapOn:
text: "Item"
index: 2 # Selects the 3rd matching element
Coordinate Selectors
# Relative position (percentage)
- tapOn:
point: 50%, 50% # Center of screen
# Absolute position (pixels)
- tapOn:
point: 100, 200 # x:100, y:200
# Tap within element
- tapOn:
text: "Large Button"
point: 90%, 50% # 90% from left, center vertically
Property Selectors
# Size-based selection
- tapOn:
width: 100
height: 50
tolerance: 10 # ±10 pixels tolerance
# State-based selection
- tapOn:
text: "Checkbox"
checked: false # Only unchecked elements
- tapOn:
id: "input_field"
focused: true # Only focused elements
- tapOn:
text: "Submit"
enabled: true # Only enabled elements
- tapOn:
text: "Tab"
selected: true # Only selected elements
Relative Position Selectors
Spatial Relationships
# Element below another
- tapOn:
below: "Header Text"
text: "Button"
# Element above another
- tapOn:
above:
id: "footer"
text: "Content"
# Element to the left
- tapOn:
leftOf: "Price"
text: "Add to Cart"
# Element to the right
- tapOn:
rightOf: "Label:"
id: "input_field"
Parent-Child Relationships
# Element containing a child
- tapOn:
containsChild: "$19.99"
# Element that is a child of another
- tapOn:
childOf:
id: "product_card"
text: "Buy Now"
# Element with multiple descendants
- tapOn:
containsDescendants:
- text: "Product Name"
- text: "$19.99"
- id: "add_to_cart"
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.
- 9d ago First seen · 366 lines · 19 tokens per session scan A 659d0513e040
maestro-selectors-instructions is a command published in the GitHub repository appboypov/pew-pew-plaza-packs (85 stars, last pushed 8mo ago), licensed MIT. It adds 19 tokens to every session and 1,791 once invoked, about $0.0001 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-09-03.
Other commands, from other repositories
web-checklist
A checklist command for testing a website after a Git merge. It records checklist items in a file so progress can be viewed and individual checks can be marked complete.
test-feature
Test a React Native feature on the running simulator/emulator. Verifies UI, user flows, and internal state. Generates a persistent Maestro test file.
qa-pr
Device-test a GitHub pull request on iOS simulator, Android emulator, and/or physical device. Installs the PR head via rn-dev-agent and reports pass/fail with repro steps and screenshots.
a11y-audit
Web accessibility (WCAG 2.1) audit command. axe-core-based checks via PageSpeed Insights.
run-workflow
Validate and establish the proven rn-dev-agent operating sequence before a real React Native journey — declared package manager and dependencies, read-only inventory, typed session recovery, one exclusive device, managed integration and Metro, only the requested proof, reverse-order cleanup.
app-runtime-verify
Verify a built mobile or app runtime at runtime: run the app (device, emulator, or headless), read the captured runtime output (native logcat, iOS device log, or the Metro/JS console), classify any runtime errors against a per-stack taxonomy, and decide a PASS/FAIL runtime gate for the slice's acceptance behavior. The…