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/patrickjs/awesome-cursorrules/android-jetpack-compose-cursorrules-prompt-filegit clone --depth 1 https://github.com/PatrickJS/awesome-cursorrulesWhat 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.00535 | $0.00535 |
| Opus 5 | $0.00267 | $0.00267 |
| Sonnet 5 | $0.00107 | $0.00107 |
| Haiku 4.5 | $0.00053 | $0.00053 |
Grade A, and why
android-jetpack-compose-cursorrules-prompt-file 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- android-jetpack-compose-cursorrules-prompt-file — 89% identical, 1 lines differ
What it actually says
// Android Jetpack Compose .cursorrules
// Flexibility Notice
// Note: This is a recommended project structure, but be flexible and adapt to existing project structures. // Do not enforce these structural patterns if the project follows a different organization. // Focus on maintaining consistency with the existing project architecture while applying Jetpack Compose best practices.
// Project Architecture and Best Practices
const androidJetpackComposeBestPractices = [ "Adapt to existing project architecture while maintaining clean code principles", "Follow Material Design 3 guidelines and components", "Implement clean architecture with domain, data, and presentation layers", "Use Kotlin coroutines and Flow for asynchronous operations", "Implement dependency injection using Hilt", "Follow unidirectional data flow with ViewModel and UI State", "Use Compose navigation for screen management", "Implement proper state hoisting and composition", ];
// Folder Structure
// Note: This is a reference structure. Adapt to the project's existing organization
const projectStructure = app/ src/ main/ java/com/package/ data/ repository/ datasource/ models/ domain/ usecases/ models/ repository/ presentation/ screens/ components/ theme/ viewmodels/ di/ utils/ res/ values/ drawable/ mipmap/ test/ androidTest/;
// Compose UI Guidelines
const composeGuidelines = `
- Use remember and derivedStateOf appropriately
- Implement proper recomposition optimization
- Use proper Compose modifiers ordering
- Follow composable function naming conventions
- Implement proper preview annotations
- Use proper state management with MutableState
- Implement proper error handling and loading states
- Use proper theming with MaterialTheme
- Follow accessibility guidelines
- Implement proper animation patterns `;
// Testing Guidelines
const testingGuidelines = `
- Write unit tests for ViewModels and UseCases
- Implement UI tests using Compose testing framework
- Use fake repositories for testing
- Implement proper test coverage
- Use proper testing coroutine dispatchers `;
// Performance Guidelines
const performanceGuidelines = `
- Minimize recomposition using proper keys
- Use proper lazy loading with LazyColumn and LazyRow
- Implement efficient image loading
- Use proper state management to prevent unnecessary updates
- Follow proper lifecycle awareness
- Implement proper memory management
- Use proper background processing `;
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 · 95 lines · 0 tokens per session scan A 15d5380a40f2
android-jetpack-compose-cursorrules-prompt-file is a cursor rule published in the GitHub repository PatrickJS/awesome-cursorrules (40,694 stars, last pushed 3mo ago), licensed CC0-1.0. It adds 535 tokens to every session, about $0.0027 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 cursor rules, from other repositories
swiftui
SwiftUI best practices for iOS, macOS, and cross-platform Apple development.
04-kotlin
Cursor rule "04-kotlin" from orbitalsonic/AndroidPilot, covering kotlin rules, prefer, coroutines, null safety and naming.
swiftui-guidelines-cursorrules-prompt-file
Cursor rule "swiftui-guidelines-cursorrules-prompt-file" from ItamarZand88/awesome-agent-conventions, covering role & perspective, code generation guidelines, 1. general principles, 2. swiftui best practices (performance first) and 3. swift 6 concurrency & threading.
swift-observable
Migration guide for updating SwiftUI apps from ObservableObject to the @Observable macro.
modern-swift
Write idiomatic SwiftUI code following Apple's latest architectural recommendations and best practices.
android_general_rules
For every Kotlin Android code you generate or refactor.