android-compose-xml-interoperability

Android guidance for combining Jetpack Compose, Android’s newer UI toolkit, with the older View-based interface system during a gradual migration.

In plain words
What is it for?
Use it for Compose screens inside fragments, traditional Android views inside Compose, shared themes, and incremental migrations.
Why use it?
It helps both UI systems work together safely while an app is updated piece by piece.

Cursor rule for Cursor

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 rules/krutikjain/android-agent-skills/android-compose-xml-interoperability
Clone the repo
git clone --depth 1 https://github.com/krutikJain/android-agent-skills

Made for: Cursor.

Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 76 The whole file, excluding the scripts and references it only reads on demand.
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.00019 $0.00076
Opus 5 $0.00010 $0.00038
Sonnet 5 $0.00004 $0.00015
Haiku 4.5 $0.00002 $0.00008

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

Security

Grade A, and why

android-compose-xml-interoperability 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.

.cursor/rules/android-compose-xml-interoperability.mdc · 10 lines

What it actually says

android-compose-xml-interoperability

Activate when the request is about compose in fragment, androidview in compose, incremental compose migration. Read skills/android-compose-xml-interoperability/SKILL.md for the canonical workflow.

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. 2d ago First seen · 10 lines · 19 tokens per session scan A ae6a5079d56a

Subscribe to this mod's changes

android-compose-xml-interoperability is a cursor rule published in the GitHub repository krutikJain/android-agent-skills (14 stars, last pushed 5mo ago), licensed MIT. It adds 19 tokens to every session and 76 once invoked, about $0.0001 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.