contexture android.instructions.md

Android development rules covering screen lifecycles, resources, manifests, and work performed on threads. Android is Google's operating system and app platform for phones and other devices.

In plain words
What is it for?
They are for guiding Android code changes involving activities, fragments, view models, listeners, resources, configuration changes, and threading.
Why use it?
They help prevent memory leaks, lost screen state, duplicate callbacks, and unsafe work on the user-interface thread.

Instructions file for GitHub Copilot

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 instructions/ackeskin/contexture/android
Clone the repo
git clone --depth 1 https://github.com/AcKeskin/contexture

Made for: GitHub Copilot.

Per session 882 This file is loaded in full into every session.
When invoked 882 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.00882 $0.00882
Opus 5 $0.00441 $0.00441
Sonnet 5 $0.00176 $0.00176
Haiku 4.5 $0.00088 $0.00088

Measured yesterday against content hash bce9b23db7aa, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

contexture android.instructions.md 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 yesterday.

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.

.github/instructions/android.instructions.md · 40 lines

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.

android rules

Auto-loaded by Copilot when editing files matching **. 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)

Read the full file on GitHub · 40 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. yesterday First seen · 40 lines · 882 tokens per session scan A bce9b23db7aa

Subscribe to this mod's changes

contexture android.instructions.md is an instructions file published in the GitHub repository AcKeskin/contexture (2 stars, last pushed 1mo ago), licensed MIT. It adds 882 tokens to every session, about $0.0044 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-31.