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 agentmods add skills/liuyi0808/android-review/compose-uinpx skills add liuyi0808/android-review --skill compose-uigit clone --depth 1 https://github.com/liuyi0808/android-reviewWrote 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/liuyi0808/android-review/compose-ui)<a href="https://agentmods.dev/skills/liuyi0808/android-review/compose-ui"><img src="https://agentmods.dev/badge/skills/liuyi0808/android-review/compose-ui.svg" alt="Measured on agentmods" 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.00085 | $0.01567 |
| Opus 5 | $0.00043 | $0.00783 |
| Sonnet 5 | $0.00017 | $0.00313 |
| Haiku 4.5 | $0.00009 | $0.00157 |
Grade A, and why
compose-ui 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 6d 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Compose UI Best Practices
Provide guidance and review for Jetpack Compose UI code following Material 3 design patterns and modern Android conventions.
Review Process
Evaluate Compose code against ALL categories. Output findings as:
[COMPOSE-XXXXX] severity: CRITICAL | HIGH | MEDIUM | LOW
Finding: <what is wrong or can be improved>
Location: <file:line>
Fix: <concrete code fix>
Reference Guide — Load on Demand
Each reference file contains full code examples and patterns. Read the relevant file when reviewing that area.
| # | Reference File | Content | When to Load |
|---|---|---|---|
| 1 | references/state-and-effects.md | State hoisting, rememberSaveable, collectAsStateWithLifecycle, LaunchedEffect, DisposableEffect, SideEffect | Reviewing state management or side effects |
| 2 | references/navigation.md | Type-safe navigation, back stack, navigation events | Reviewing navigation setup |
| 3 | references/theming.md | Material 3 tokens, dynamic colors, custom extensions | Reviewing theme or color usage |
| 4 | references/accessibility.md | Content descriptions, touch targets, semantics merging | Reviewing accessibility compliance |
| 5 | references/layout-and-animation.md | WindowSizeClass, responsive layout, AnimatedVisibility, animateXAsState | Reviewing layout or animation code |
Rules Summary
State Management
- State ownership: state hoisted to the lowest common ancestor.
- Use
rememberSaveablefor state that survives configuration changes. - Complex state belongs in ViewModel, exposed as
StateFlow. See architecture skill for ViewModel implementation patterns. - ALWAYS use
collectAsStateWithLifecycle()(NOTcollectAsState()). - Use sealed interface for UI state.
Side Effects
LaunchedEffectfor coroutine-based side effects.DisposableEffectfor cleanup-requiring side effects.SideEffectfor non-suspend side effects on every successful recomposition.rememberCoroutineScopefor event-triggered coroutines.- NEVER launch coroutines directly in Composable body.
What ships with it
5 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.
- 6d ago First seen · 189 lines · 85 tokens per session scan A 8ceae7197721
compose-ui is a skill published in the GitHub repository liuyi0808/android-review (11 stars, last pushed 10d ago), licensed MIT. It adds 85 tokens to every session and 1,567 once invoked, about $0.0004 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
display-glasses-with-jetpack-compose-glimmer
Provides guidelines for developing projected Android XR apps for display glasses using the Jetpack Compose Glimmer UI toolkit. This skill covers foundational Glimmer design principles, workflows for implementing Jetpack Compose Glimmer, and interaction models for the glasses form factor. Use this skill to build an…
expo-design-system
Framework (OSS). Build and maintain a design system inside an Expo app - a reusable theme of design tokens (color, spacing, typography, radius, shadow, motion), reusable component structure with variant/size/state prop conventions, and rules for when to extract a repeated view into a shared component. Use when…
flutter-build-responsive-layout
Use LayoutBuilder, MediaQuery, or Expanded/Flexible to create a layout that adapts to different screen sizes. Use when you need the UI to look good on both mobile and tablet/desktop form factors.
platform-conventions
Design to iOS and Android conventions — what each OS mandates, where they diverge, and when to unify. Use when shipping native apps. For breakpoint adaptation use responsive-design; for matching competitor patterns use jakobs-law (interaction-design).
field-service-mobile-branding-configure
Derive a Field Service mobile app color scheme from a brand source (URL, hex codes, brand-guide paste, or color description), validate WCAG AA contrast in both light and dark mode, and apply the 14-field scheme to the org-default FieldServiceMobileSettings record. Trigger phrases include 'brand the mobile app', 'apply…
app-ui-design
Mobile app UI design expert for iOS and Android. Use when designing app interfaces, creating design systems, ensuring accessibility, or following platform guidelines. Covers Material Design 3, Human Interface Guidelines, color theory, typography, and 2025 trends.