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 tmolavi/mcp-agent-skills-hub --skill migrate-xml-views-to-jetpack-composegit clone --depth 1 https://github.com/tmolavi/mcp-agent-skills-hubWrote 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/tmolavi/mcp-agent-skills-hub/migrate-xml-views-to-jetpack-compose)<a href="https://agentmods.dev/skills/tmolavi/mcp-agent-skills-hub/migrate-xml-views-to-jetpack-compose"><img src="https://agentmods.dev/badge/skills/tmolavi/mcp-agent-skills-hub/migrate-xml-views-to-jetpack-compose/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/tmolavi/mcp-agent-skills-hub/migrate-xml-views-to-jetpack-compose"><img src="https://agentmods.dev/badge/skills/tmolavi/mcp-agent-skills-hub/migrate-xml-views-to-jetpack-compose.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.00098 | $0.01191 |
| Opus 5 | $0.00049 | $0.00596 |
| Sonnet 5 | $0.00020 | $0.00238 |
| Haiku 4.5 | $0.00010 | $0.00119 |
Grade A, and why
migrate-xml-views-to-jetpack-compose 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.
This is a copy
97% identical to migrate-xml-views-to-jetpack-compose — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
This skill guides through the process of migrating an existing Android XML View to Jetpack Compose. It performs a stable, safe and visually consistent transition by following a structured, 10-step methodology. This skill migrates UI (XML to Jetpack Compose) only.
Objective
To systematically convert a single legacy XML layout into modern, declarative Jetpack Compose UI while maintaining pixel-perfect visual parity and functional integrity.
Summary of the 10-step migration process
- Identify the optimal XML candidate for migration
- Analyze the project and layout
- Create a plan
- Capture the XML View UI
- Set up Compose dependencies and compiler
- Set up Compose theming
- Migrate the XML layout to Compose
- Validate the migration
- Replace usages
- XML code removal
Detailed steps
Step 1: Identify the optimal XML candidate for migration
If the user has explicitly specified a target XML layout, proceed to Step 2. Otherwise, analyze the codebase to identify the best candidate for migration by following the logic in references/identify-optimal-xml-candidate.md.
Step 2: Analyze the project and layout
Analyze the identified XML View's structure, hierarchy, and implementation details. Use references/analysis-of-the-project-and-layout.md to guide your technical audit of the layout and surrounding project context.
Step 3: Create a plan
Using the outputs and analysis done in the Step 1 and 2, generate a step-by-step plan for the migration. If you support user interaction, present to the user and ask for approval before proceeding. If user interaction is not supported, proceed to Step 4 following the generated plan.
Step 4: Capture the XML View UI
IF you support user interaction, ask the user to upload a screenshot of the XML View UI or provide an absolute path to a file. Use this image as a visual reference for the layout migration in Step 7. ELSE IF you are able to run an Android emulator, locate an existing screenshot test for the XML candidate. If none exists, create one using the existing project testing framework. If no framework exists, use UI Automator or Espresso to create a screenshot test with minimum required setup. Run the test and take a baseline screenshot of the XML UI. ELSE proceed to Step 5.
What ships with it
7 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.
- references/analysis-of-the-project-and-layout.md 3.1 KB
- references/android/develop/ui/compose/designsystems/migrate-xml-theme-to-compose.md 8.1 KB
- references/android/develop/ui/compose/migrate/interoperability-apis/compose-in-views.md 12 KB
- references/android/develop/ui/compose/migrate/interoperability-apis/views-in-compose.md 11 KB
- references/android/develop/ui/compose/setup-compose-dependencies-and-compiler.md 7.3 KB
- references/identify-optimal-xml-candidate.md 1.6 KB
- references/xml-layout-migration.md 3.5 KB
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 · 125 lines · 98 tokens per session scan A a8b0bcdadbb9
migrate-xml-views-to-jetpack-compose is a skill published in the GitHub repository tmolavi/mcp-agent-skills-hub (8 stars, last pushed 17d ago), licensed MIT. It adds 98 tokens to every session and 1,191 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to migrate-xml-views-to-jetpack-compose, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
Apple Human Interface Guidelines (HIG) Design
Apple Human Interface Guidelines (HIG) design and development standards for iOS, macOS, and visionOS. / TR: iOS, macOS ve visionOS için Apple Human Interface Guidelines (İnsan Arayüzü Yönergeleri) tabanlı uygulama tasarımı ve geliştirme becerisi.
swift-architecture-auditor
Swift & iOS/macOS mimari inceleme, SwiftUI/UIKit katman analizi, MVVM/VIPER/TCA kontrolü, Concurrency ve Memory Leak denetim skilli.
data-pro-skill
Market research data analysis meta-prompt. Transforms raw quantitative and qualitative data into dense, Tufte-style analytical documents. Document-driven. Invisible agent loop: Statistician -> Critic -> Tufte Designer. Commands: /dps-setup, /dps-cross, /dps-inject-open, /dps-export. Modes: /dps-mode:quant…
android_ui_verification
Automated end-to-end UI testing and verification on an Android Emulator using ADB.
asc-shots-pipeline
Orchestrate iOS screenshot automation with xcodebuild/simctl for build-run, AXe for UI actions, JSON settings and plan files, Koubou-based framing (asc screenshots frame), and screenshot upload (asc screenshots upload). Use when users ask for automated screenshot capture, AXe-driven simulator flows, frame composition…
asc-workflow
Define, validate, run, resume, and audit repo-local multi-step automations with current asc workflow and .asc/workflow.json, including step outputs and safe release/TestFlight workflows.