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 hanamizuki/solopreneur --skill compose-uigit clone --depth 1 https://github.com/hanamizuki/solopreneurWrote 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/hanamizuki/solopreneur/compose-ui)<a href="https://agentmods.dev/skills/hanamizuki/solopreneur/compose-ui"><img src="https://agentmods.dev/badge/skills/hanamizuki/solopreneur/compose-ui/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/hanamizuki/solopreneur/compose-ui"><img src="https://agentmods.dev/badge/skills/hanamizuki/solopreneur/compose-ui.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.00039 | $0.00612 |
| Opus 5 | $0.00019 | $0.00306 |
| Sonnet 5 | $0.00008 | $0.00122 |
| Haiku 4.5 | $0.00004 | $0.00061 |
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 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
100% identical to compose-ui — 0 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jetpack Compose Best Practices
Instructions
Follow these guidelines to create performant, reusable, and testable Composables.
1. State Hoisting (Unidirectional Data Flow)
Make Composables stateless whenever possible by moving state to the caller.
- Pattern: Function signature should usually look like:
@Composable fun MyComponent( value: String, // State flows down onValueChange: (String) -> Unit, // Events flow up modifier: Modifier = Modifier // Standard modifier parameter ) - Benefit: Decouples the UI from simple state storage, making it easier to preview and test.
- ViewModel Integration: The screen-level Composable retrieves state from the ViewModel (
viewModel.uiState.collectAsStateWithLifecycle()) and passes it down.
2. Modifiers
- Default Parameter: Always provide a
modifier: Modifier = Modifieras the first optional parameter. - Application: Apply this
modifierto the root layout element of your Composable. - Ordering matters:
padding().clickable()is different fromclickable().padding(). Generally apply layout-affecting modifiers (like padding) after click listeners if you want the padding to be clickable.
3. Performance Optimization
remember: Useremember { ... }to cache expensive calculations across recompositions.derivedStateOf: UsederivedStateOf { ... }when a state changes frequently (like scroll position) but the UI only needs to react to a threshold or summary (e.g., show "Jump to Top" button). This prevents unnecessary recompositions.val showButton by remember { derivedStateOf { listState.firstVisibleItemIndex > 0 } }- Lambda Stability: Prefer method references (e.g.,
viewModel::onEvent) or remembered lambdas to prevent unstable types from triggering recomposition of children.
4. Theming and Resources
- Use
MaterialTheme.colorSchemeandMaterialTheme.typographyinstead of hardcoded colors or text styles. - Organize simple UI components into specific files (e.g.,
DesignSystem.ktorComponents.kt) if they are shared across features.
What ships with it
1 file 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 · 50 lines · 39 tokens per session scan A e1d56573ba5f
compose-ui is a skill published in the GitHub repository hanamizuki/solopreneur (148 stars, last pushed 24d ago), licensed MIT. It adds 39 tokens to every session and 612 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to compose-ui, differing in 0 lines, and is treated as a copy.
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.
omh-apple-design
This is a Hermes-native apple-design workflow skill.
axiom-audit-liquid-glass
Use when the user mentions Liquid Glass review, iOS 26 UI updates, toolbar improvements, or visual effect migration.
axiom-audit-ux-flow
Use when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app.