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 agentmods add rules/duckduckgo/apple-browsers/maestro-device-selectiongit clone --depth 1 https://github.com/duckduckgo/apple-browsersWrote 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/rules/duckduckgo/apple-browsers/maestro-device-selection)<a href="https://agentmods.dev/rules/duckduckgo/apple-browsers/maestro-device-selection"><img src="https://agentmods.dev/badge/rules/duckduckgo/apple-browsers/maestro-device-selection.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00942 |
| Opus 5 | $0.00000 | $0.00471 |
| Sonnet 5 | $0.00000 | $0.00188 |
| Haiku 4.5 | $0.00000 | $0.00094 |
Grade A, and why
maestro-device-selection 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 3d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Maestro Test Device Selection (iPhone/iPad)
Overview
Maestro tests can run on either iPhone or iPad simulators based on tags in the test YAML files. This allows you to test iPad-specific UI layouts and features while maintaining a single test suite.
How It Works
- Default: Tests run on iPhone 16 with iOS 18.2
- iPad Tests: Add
ipadtag to run on iPad 10th generation with iOS 18.2
Usage
For Individual iPad Tests
Add the ipad tag to your test file:
appId: com.duckduckgo.mobile.ios
tags:
- ipad
- your-other-tags
name: Your iPad Test
---
# Your test steps here
Running Tests
The same commands work as before:
# Run a single test (device selected based on tags)
./run_ui_tests.sh path/to/test.yaml
# Run all tests in a folder (each test runs on appropriate device)
./run_ui_tests.sh path/to/tests/
Implementation Details
Setup Phase (setup_ui_tests.sh)
- Creates both iPhone and iPad simulators upfront
- Boots and configures both simulators with English locale
- Installs the app on both devices
- Saves both simulator UUIDs for test execution
Test Execution (run_ui_tests.sh)
- Opens Simulator app if not already running
- Checks each test file for the
ipadtag using grep - Boots the required simulator if it's not already running
- Uses the pre-created simulator based on the tag
- Reinstalls the app before each test for clean state
- Reports which device type was used in test results
Simulator Specifications
- iPhone: iPhone 16, iOS 18.2
- iPad: iPad (10th generation), iOS 18.2
Both simulators are configured with:
- Language: English (en)
- Locale: en_US
- Name suffix: "(maestro)" for easy identification
Example Test Structure
appId: com.duckduckgo.mobile.ios
tags:
- ipad
- duckplayer
name: DuckPlayer iPad Layout Test
---
# This test will automatically run on iPad simulator
- runFlow:
file: ../shared/setup.yaml
# Test iPad-specific UI elements
- assertVisible: "Split View" # Example iPad-specific element
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.
- 3d ago First seen · 132 lines · 0 tokens per session scan A 5e9e6f47ef0f
maestro-device-selection is a cursor rule published in the GitHub repository duckduckgo/apple-browsers (251 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 942 tokens. 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-01.
Other cursor rules, from other repositories
react-native-debugger-mcp
使用 react-native-debugger-mcp 工具讀取 React Native 台日誌.
create-ios-release
As an AI assistant helping with iOS app releases, I should guide through the following process for successfully deploying iOS applications to the App Store.
203-healthkit-integration-detailed
HealthKit & WorkoutKit 集成规范 - 详细参考.
010-healthkit-workoutkit
010: HealthKit and WorkoutKit integration patterns for iOS health apps.
main-refactoring-rules
ios cursor rules.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.