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 skills add GDvega/super-android-kotlin-firebase-skill --skill xml-to-compose-migrationgit clone --depth 1 https://github.com/GDvega/super-android-kotlin-firebase-skillWrote 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/skills/gdvega/super-android-kotlin-firebase-skill/xml-to-compose-migration)<a href="https://agentmods.dev/skills/gdvega/super-android-kotlin-firebase-skill/xml-to-compose-migration"><img src="https://agentmods.dev/badge/skills/gdvega/super-android-kotlin-firebase-skill/xml-to-compose-migration/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/skills/gdvega/super-android-kotlin-firebase-skill/xml-to-compose-migration"><img src="https://agentmods.dev/badge/skills/gdvega/super-android-kotlin-firebase-skill/xml-to-compose-migration.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.00030 | $0.00710 |
| Opus 5 | $0.00015 | $0.00355 |
| Sonnet 5 | $0.00006 | $0.00142 |
| Haiku 4.5 | $0.00003 | $0.00071 |
Grade A, and why
xml-to-compose-migration 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Move legacy XML UI to Compose incrementally while preserving resources, navigation, ViewModel logic and test coverage.
When to use
- Converting XML layout screens to Compose.
- Migrating ViewBinding or Fragment UI to Compose.
- Keeping XML and Compose interoperability during a transition.
- Migrating themes, colors and strings into Compose-friendly usage.
Inputs to inspect
res/layout/*.xmlFragment.ktandActivity.kt- ViewBinding usage
themes.xml,colors.xml,strings.xml- Navigation graph and screen tests
Required workflow
- Identify the smallest screen or component to migrate.
- Keep business logic in ViewModel or domain layers.
- Use ComposeView or route/screen split for incremental adoption.
- Preserve strings and accessibility labels.
- Add previews and critical UI tests.
Rules
- Do not delete XML that is still referenced.
- Do not move ViewModel logic into Composables.
- Keep string resources in resources unless project conventions differ.
- Preserve navigation contracts.
- Prefer incremental migration over large rewrites.
Related existing skills
Local skills to invoke
- jetpack-compose
- edge-to-edge-adaptive-ui
- accessibility
- testing
External companion skills to use when installed
Do not assume these companion skills are installed. Prefer the local skills above first, then consult Companion Skills for install and verification commands.
- aldefy/compose-skill — use for deeper Jetpack Compose, Material 3, design-to-code, theming or Compose architecture guidance.
- android/skills — use for official Android workflow alignment around edge-to-edge, adaptive UI, Navigation 3, R8, AGP or testing setup.
Files commonly touched
res/layout/*.xmlFragment.ktActivity.ktfeature/*/*Screen.ktui/theme/*navigation/*androidTest/*
Commands to validate
./gradlew assembleDebug
./gradlew test
./gradlew connectedDebugAndroidTest
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 108 lines · 30 tokens per session scan A 812e6acb0953
xml-to-compose-migration is a skill published in the GitHub repository GDvega/super-android-kotlin-firebase-skill (2 stars, last pushed 2mo ago), licensed MIT. It adds 30 tokens to every session and 710 once invoked, about $0.0002 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.
Other skills, from other repositories
android-studio
Operational skill for Android Studio: Gradle projects, emulators, Logcat, build variants, signing configs, and AGP troubleshooting.
analyzing-android-malware-with-apktool
Perform static analysis of Android APK malware using apktool for resource decompilation, jadx for Java source recovery, and androguard for manifest inspection, dangerous permission-combination detection, and identification of obfuscated code, dynamic code loading, and reflection-based API calls. Use to statically…
solopi-ai
A command-line framework for testing Android apps and devices with SoloPi, including on-device or cloud AI decision models. It manages devices, test cases, recorded interactions, replays, performance history, and evidence.
app-store-preflight-compliance
Pre-submission compliance scanner workflow for Apple App Store apps. Use when reviewing iOS, macOS, tvOS, watchOS, or visionOS projects (Swift, Objective-C, React Native, Expo) for App Store rejection risks, submission readiness, privacy compliance, or guideline violations.
ios-slim-bindings
Create iOS slim bindings for MAUI. USE FOR: slim iOS binding, Native Library Interop, Swift/Objective-C wrappers, XcodeGen project.yml, Podfile, CocoaPods static linking, BUILDLIBRARYFORDISTRIBUTION, XcodeProject MSBuild, @objc/[Export] selector crashes, async completion handlers. DO NOT USE FOR: Android bindings…
maui-auth-secure-storage
Implement MAUI auth and secure storage. USE FOR: WebAuthenticator/MSAL, OAuth/OIDC redirects, Entra ID, callback URIs, Android intent filters, CFBundleURLTypes, token cache cleanup, SecureStorage, logout, Blazor Hybrid auth handoff. DO NOT USE FOR: architecture, API retries/offline data, UI debugging.