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/AcKeskin/contextureWrote 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/ackeskin/contexture/android)<a href="https://agentmods.dev/rules/ackeskin/contexture/android"><img src="https://agentmods.dev/badge/rules/ackeskin/contexture/android/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/ackeskin/contexture/android"><img src="https://agentmods.dev/badge/rules/ackeskin/contexture/android.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.00000 | $0.00879 |
| Opus 5.5 | $0.00000 | $0.00352 |
| Sonnet 5.5 | $0.00000 | $0.00176 |
| Haiku 4.5 | $0.00000 | $0.00088 |
Grade A, and why
android 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 today.
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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generated from
architectural-rules/android/— do not hand-edit.
Android Lifecycle Discipline
Never hold a static or long-lived reference to an Activity, Fragment, View, or their Context. Use applicationContext for needs that outlive a single screen. A static Activity ref keeps the whole view hierarchy alive past onDestroy, leaking memory. (Android docs — Activity lifecycle)
Do not store UI state in the Activity/Fragment. Hold it in a ViewModel (survives rotation/config changes) plus SavedStateHandle / saved instance state for process death. The system destroys and recreates the Activity on configuration change; instance fields are lost. (Android docs — Handle configuration changes)
Register and unregister listeners, receivers, sensors, and observers symmetrically: acquire in onStart/onResume, release in the paired onStop/onPause. Asymmetric registration leaks callbacks and double-fires after recreation. (Android docs — Activity lifecycle)
Why: The framework owns Activity/Fragment lifetime and recreates them on configuration changes, so any UI state or Context captured in instance/static fields either leaks or is silently lost. Hoisting state into a lifecycle-aware ViewModel and binding resource acquisition to symmetric lifecycle callbacks keeps ownership explicit and prevents both leaks and stale callbacks. Source: Android developer documentation.
Android Resources and Manifest Discipline
Never hardcode UI strings, dimensions, colors, or sizes in code or layouts. Put them in res/values/ (strings.xml, dimens.xml, colors.xml) and provide configuration-qualified variants (values-fr/, values-night/, values-sw600dp/). Externalized resources enable localization, theming, and device adaptation. (Android docs — App resources)
Declare every permission in the manifest, and for dangerous permissions request them at runtime and handle denial gracefully. Assuming a permission is granted without checking crashes on modern Android. Request only what the feature needs. (Android docs — Permissions on Android)
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.
- today First seen · 40 lines · 879 tokens per session scan A ae0296ccb9d4
android is a cursor rule published in the GitHub repository AcKeskin/contexture (2 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 879 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-10-27.
Other cursor rules, from other repositories
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.
hatch3r-flutter-patterns
Flutter and Dart conventions covering null safety, state management (Riverpod/Bloc), Material 3, FFI, performance, platform channels, and integration testing.
hatch3r-swiftui-patterns
SwiftUI and Swift conventions covering Swift 6 concurrency, @Observable + @Bindable, navigation stacks, Swift Package Manager, modular architecture, and XCTest.
android-jetpack-compose-cursorrules-prompt-file
description: "Cursor rules for Android development with Jetpack Compose integration." globs: / alwaysApply: false.
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.
compose-coroutines
Compose scroll/coroutine patterns — prevent programmatic scroll from being mistaken for user scroll, cancellation-safe flag resets.