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/toptalentcoder/cursor-awesomerules/android-jetpack-compose-performance-guidelinesgit clone --depth 1 https://github.com/toptalentcoder/Cursor-AwesomeRulesWhat 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.00083 |
| Opus 5 | $0.00000 | $0.00042 |
| Sonnet 5 | $0.00000 | $0.00017 |
| Haiku 4.5 | $0.00000 | $0.00008 |
Grade A, and why
android-jetpack-compose---performance-guidelines 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.
This is a copy
100% identical to android-jetpack-compose---performance-guidelines — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
- 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.
- 2d ago First seen · 11 lines · 0 tokens per session scan A 4a3ffd94d8e9
android-jetpack-compose---performance-guidelines is a cursor rule published in the GitHub repository toptalentcoder/Cursor-AwesomeRules (6 stars, last pushed 1y ago), licensed CC0-1.0. It costs nothing until one of its globs matches a file; then it loads 83 tokens. A static security scan graded it A with 0 findings. It is 100% identical to android-jetpack-compose---performance-guidelines, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
android-viewmodel
Android ViewModel conventions — StateFlow, repository abstraction, coroutines, no LiveData.
cursorrules
ROLE: Android Development Expert EXPERIENCELEVEL: Advanced (10+ years) SPECIALTIES.
trove-swift
Swift 6 and SwiftUI coding conventions for iOS development. Auto-activates when working with Swift files. Covers @Observable, async/await, NavigationStack, Swift Testing, and accessibility.
20-android-kotlin
There is no Android SDK/NDK available in most sandboxed dev environments (including the one this codebase was originally scaffolded in). Kotlin code in this repo has generally not been compiled or run by an AI agent — only reviewed for logical consistency. Treat Kotlin changes as higher-risk than Rust changes until a…
getting-started
SDK setup, Swift Package Manager integration, Info.plist configuration, and first connection to Meta glasses.
swift-implementation
Swift and SwiftUI implementation expectations for app code.