cursorrules

A set of rules for building Appium tests, which automate Android and iOS apps, across different devices, operating systems, and app types.

In plain words
What is it for?
It is for structuring mobile test projects, locating elements, handling gestures and waits, managing devices and emulators, and installing, resetting, or cleaning up apps.
Why use it?
It addresses differences between platforms, screen sizes, app states, device setups, and native or web-based app views.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/tugkanboz/awesome-cursorrules/cursorrules
Clone the repo
git clone --depth 1 https://github.com/tugkanboz/awesome-cursorrules

Made for: Cursor.

Per session 400 This file is loaded in full into every session.
When invoked 400 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00400 $0.00400
Opus 5 $0.00200 $0.00200
Sonnet 5 $0.00080 $0.00080
Haiku 4.5 $0.00040 $0.00040

Measured 2d ago against content hash 7e66268f726e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cursorrules 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 2d 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.

rules/appium-mobile-test-automation-framework/.cursorrules · 82 lines

How it starts

The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Project: Appium Mobile Test Automation Framework

Framework Structure

  • Support both Android and iOS platforms
  • Use Page Object Model pattern
  • Implement proper test hierarchy
  • Create platform-specific implementations

Coding Standards

  • Follow language-specific conventions (Java/Python)
  • Use proper naming conventions
  • Implement clean code principles
  • Maximum method length: 30 lines

Mobile Elements Strategy

  • Use proper element locator strategies
  • Implement gestures handling
  • Handle native, hybrid, and web contexts
  • Create reusable mobile actions

Test Organization

  • Group tests by features/screens
  • Implement test priorities
  • Create separate suites for platforms
  • Use proper test categorization

Best Practices

  • Handle app states properly
  • Implement proper waiting strategies
  • Use proper capability management
  • Handle different screen sizes/resolutions
  • Implement proper cleanup

Device Management

  • Handle real devices and emulators
  • Implement device farms integration
  • Manage app installation/uninstallation
  • Handle different OS versions

Application Management

  • Handle app lifecycle
  • Manage app permissions
  • Handle app reset strategies
  • Implement proper app configuration

Test Data

  • Manage test data for different platforms
  • Handle localization testing
  • Implement data-driven tests
  • Keep sensitive data secure

Reporting

  • Generate platform-specific reports
  • Include screenshots and videos
  • Log device information
  • Track test execution metrics

Performance Monitoring

  • Monitor app performance
  • Track memory usage
  • Measure app launch time
  • Monitor battery consumption

CI/CD Integration

  • Configure for different CI platforms
  • Handle parallel execution
  • Manage device allocation
  • Configure test distribution

Error Handling

  • Implement proper exception handling
  • Create recovery mechanisms
  • Handle device-specific errors
  • Implement retry mechanisms

Documentation

  • Document setup requirements
  • Maintain platform-specific guides
  • Include troubleshooting guides
  • Document known issues

Read the full file on GitHub · 82 lines

Changes

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.

  1. 2d ago First seen · 82 lines · 400 tokens per session scan A 7e66268f726e

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository tugkanboz/awesome-cursorrules (20 stars, last pushed 3d ago), licensed MIT. It adds 400 tokens to every session, about $0.0020 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.