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 new-silvermoon/awesome-android-agent-skills --skill xml-to-compose-migrationgit clone --depth 1 https://github.com/new-silvermoon/awesome-android-agent-skillsWrote 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/new-silvermoon/awesome-android-agent-skills/xml-to-compose-migration)<a href="https://agentmods.dev/skills/new-silvermoon/awesome-android-agent-skills/xml-to-compose-migration"><img src="https://agentmods.dev/badge/skills/new-silvermoon/awesome-android-agent-skills/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/new-silvermoon/awesome-android-agent-skills/xml-to-compose-migration"><img src="https://agentmods.dev/badge/skills/new-silvermoon/awesome-android-agent-skills/xml-to-compose-migration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 117 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- high Prompt Injection · line 175 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
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.00041 | $0.02481 |
| Opus 5 | $0.00020 | $0.01241 |
| Sonnet 5 | $0.00008 | $0.00496 |
| Haiku 4.5 | $0.00004 | $0.00248 |
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 11d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- xml-to-compose-migration — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 339 lines — stays where its author put it; the contents beside it link to each section on GitHub.
XML to Compose Migration
Overview
Systematically convert Android XML layouts to idiomatic Jetpack Compose, preserving functionality while embracing Compose patterns. This skill covers layout mapping, state migration, and incremental adoption strategies.
Workflow
1. Analyze the XML Layout
- Identify the root layout type (
ConstraintLayout,LinearLayout,FrameLayout, etc.). - List all View widgets and their key attributes.
- Map data binding expressions (
@{}) or view binding references. - Identify custom views that need special handling.
- Note any
include,merge, orViewStubusage.
2. Plan the Migration
- Decide: Full rewrite or incremental migration (using
ComposeView/AndroidView). - Identify state sources (ViewModel, LiveData, savedInstanceState).
- List reusable components to extract as separate Composables.
- Plan navigation integration if using Navigation component.
3. Convert Layouts
Apply the layout mapping table below to convert each View to its Compose equivalent.
4. Migrate State
- Convert
LiveDataobservation toStateFlowcollection orobserveAsState(). - Replace
findViewById/ ViewBinding with Compose state. - Convert click listeners to lambda parameters.
5. Test and Verify
- Compare visual output between XML and Compose versions.
- Test accessibility (content descriptions, touch targets).
- Verify state preservation across configuration changes.
Layout Mapping Reference
Container Layouts
| XML Layout | Compose Equivalent | Notes |
|---|---|---|
LinearLayout (vertical) |
Column |
Use Arrangement and Alignment |
LinearLayout (horizontal) |
Row |
Use Arrangement and Alignment |
FrameLayout |
Box |
Children stack on top of each other |
ConstraintLayout |
ConstraintLayout (Compose) |
Use createRefs() and constrainAs |
RelativeLayout |
Box or ConstraintLayout |
Prefer Box for simple overlap |
ScrollView |
Column + Modifier.verticalScroll() |
Or use LazyColumn for lists |
HorizontalScrollView |
Row + Modifier.horizontalScroll() |
Or use LazyRow for lists |
RecyclerView |
LazyColumn / LazyRow / LazyGrid |
Most common migration |
ViewPager2 |
HorizontalPager |
From accompanist or Compose Foundation |
CoordinatorLayout |
Custom + Scaffold |
Use TopAppBar with scroll behavior |
NestedScrollView |
Column + Modifier.verticalScroll() |
Prefer Lazy variants |
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.
- 11d ago First seen · 339 lines · 41 tokens per session scan A e9f1eb49e59f
xml-to-compose-migration is a skill published in the GitHub repository new-silvermoon/awesome-android-agent-skills (955 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 41 tokens to every session and 2,481 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-30.
Other skills, from other repositories
wear-compose-m3
Expert guidance for working with Wear OS Compose Material3. Use this skill when creating, updating, or migrating Wear OS projects. This includes the androidx.wear.compose.material3, androidx.wear.compose.foundation, and androidx.wear.compose.navigation3 libraries. Also working with core components such as AppScaffold…
kotlin-specialist
Provides idiomatic Kotlin implementation patterns including coroutine concurrency, Flow stream handling, multiplatform architecture, Compose UI construction, Ktor server setup, and type-safe DSL design. Use when building Kotlin applications requiring coroutines, multiplatform development, or Android with Compose.…
build-android-binary
Compile a PAM control's Android Kotlin module into the runtime-loadable DEX for a .ppmplugin. Creates a staged Gradle build with the pinned wrapper and react-android compile dependency, verifies manifest/module/package alignment and runtime-loading constraints, builds the release AAR, then runs d8 --min-api 24. Writes…
swiftui-dev
Use this skill for SwiftUI development, architecture, structure, performance, and Apple native app profiling. It combines.
android-navigation-3
Install and migrate to Jetpack Navigation 3. Use when implementing Navigation 3 patterns including NavDisplay, NavKey routes, deep links, multiple backstacks, scenes (dialogs, bottom sheets), or migrating from Navigation 2.
mobiai-kmp
Use when working on a Kotlin Multiplatform project — shared code, expect/actual declarations, platform-specific implementations, building and testing.