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/preshan/GroceryListWrote 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/preshan/grocerylist/android-architecture)<a href="https://agentmods.dev/rules/preshan/grocerylist/android-architecture"><img src="https://agentmods.dev/badge/rules/preshan/grocerylist/android-architecture/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/rules/preshan/grocerylist/android-architecture"><img src="https://agentmods.dev/badge/rules/preshan/grocerylist/android-architecture.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.00307 | $0.00307 |
| Opus 5.5 | $0.00123 | $0.00123 |
| Sonnet 5.5 | $0.00061 | $0.00061 |
| Haiku 4.5 | $0.00031 | $0.00031 |
Grade A, and why
android-architecture 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 1mo 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.
What it actually says
Android Architecture Rules
Use:
- Kotlin
- Jetpack Compose
- Room SQLite
- Navigation Compose
- ViewModel
- Coroutines / Flow where useful
Preferred package structure:
app/src/main/java/com/preshan/grocerylist/
data/local/entitydata/local/daodata/local/databasedata/repositorydomain/modeldomain/usecaseui/navigationui/screens/homeui/screens/quickselectui/screens/shoppingui/screens/manageitemsui/screens/settingsui/componentsui/themeutil
Rules:
- Keep business logic out of Composables.
- Use ViewModels for screen state.
- Use repositories for data access.
- Do not create backend/API code.
- Do not add unnecessary dependencies.
- Keep code simple and readable.
- Use Room migrations carefully.
- Do not add AdMob until core offline flow is working.
Additional implementation guardrails:
- Keep composables stateless where possible; hoist mutable UI state to ViewModel.
- Expose immutable
StateFlow/UI state models from ViewModel. - Keep DAO interfaces focused and transaction logic inside repository/database layer.
- Add migrations explicitly for schema changes; do not rely on destructive migration in release builds.
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.
- 1mo ago First seen · 52 lines · 307 tokens per session scan A 1ed44c9daf9f
android-architecture is a cursor rule published in the GitHub repository preshan/GroceryList (2 stars, last pushed 5mo ago), licensed MIT. It adds 307 tokens to every session, about $0.0012 per session on Opus 5.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-31.
Other cursor rules, from other repositories
swiftui-guidelines-cursorrules-prompt-file
Cursor rules for SwiftUI development guidelines.
gradle
Enforce modern Gradle build practices for Java and Android projects, focusing on Kotlin DSL, modularity, version catalogs, and performance optimizations.
compose-coroutines
Compose scroll/coroutine patterns — prevent programmatic scroll from being mistaken for user scroll, cancellation-safe flag resets.
android-viewmodel
Android ViewModel conventions — StateFlow, repository abstraction, coroutines, no LiveData.
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.
hatch3r-android-patterns
Android Kotlin conventions covering Jetpack Compose, coroutines + Flow, Hilt DI, Room, modular Gradle, AGP 8.x, target SDK 35, and Compose testing.