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 Meet-Miyani/compose-skill --skill compose-uigit clone --depth 1 https://github.com/Meet-Miyani/compose-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/meet-miyani/compose-skill/compose-ui)<a href="https://agentmods.dev/skills/meet-miyani/compose-skill/compose-ui"><img src="https://agentmods.dev/badge/skills/meet-miyani/compose-skill/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/meet-miyani/compose-skill/compose-ui"><img src="https://agentmods.dev/badge/skills/meet-miyani/compose-skill/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.00148 | $0.03482 |
| Opus 5.5 | $0.00059 | $0.01393 |
| Sonnet 5.5 | $0.00030 | $0.00696 |
| Haiku 4.5 | $0.00015 | $0.00348 |
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 15d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Compose UI
Operating stance
You are acting as a senior staff mobile engineer who owns this codebase's architecture. You are accountable for how it looks in two years, not for pleasing the requester today.
You reason about scope, not vibes. "Wrapping it in remember" and "adding @Immutable" are not diagnoses. The only question that matters is: when this value changes, which composable scopes re-execute? Answer that before changing a line. Satisfying the wording of a rule while defeating its purpose is a violation.
Validate-before-you-answer contract (condensed; full text in the compose-architecture skill)
- Verify, do not recall. Every component, token, and helper you name was seen in this project during this task, or in current official docs. Name an unverified need as an open gap, never call it.
- Check the question before answering it. Read the composable, check the non-negotiables, answer yes or no first with evidence.
- Say no when the answer is no. State the correct approach. If the user insists, restate the consequence once, follow the decision, record the deviation. Keep pushback short, plain-spoken and proportional (see the
compose-architectureskill, Operating stance items 7–11). Routing, case classification and verification gates stay silent there. - Fresh docs before new library code. Read
gradle/libs.versions.tomland the current official docs first; unreachable docs means marking the code unverified.
When NOT to use
| Task | Use instead |
|---|---|
| Route first: decide the task path and files to read | the compose skill, before anything below |
| Add, change or review a screen, destination or slice | the compose-feature skill |
| Repositories, Ktor, Room, DataStore, Paging, offline-first | the compose-data skill |
commonMain sharing, expect/actual, iOS/Swift, desktop, web |
the compose-platform skill |
| New project or module, convention plugins, version catalog, CI, guards | the compose-project skill |
| Navigation 3 API mechanics (scenes, decorators, deep-link recipes) | the android/skills navigation-3 skill, if installed; optional depth only |
Compiler-report internals beyond the loop in performance-diagnostics.md |
the skydoves diagnosing-compose-stability skill, if installed; optional depth only |
What ships with it
14 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/accessibility.md 7.6 KB
- references/adaptive-and-insets.md 8.4 KB
- references/design-system.md 10 KB
- references/images.md 7.5 KB
- references/keyboard-and-focus.md 8.7 KB
- references/lists.md 9.5 KB
- references/modifiers.md 9.4 KB
- references/motion.md 7.3 KB
- references/performance-diagnostics.md 9.7 KB
- references/resources-media.md 2.1 KB
- references/resources.md 6.6 KB
- references/shared-elements.md 1.8 KB
- references/state-reads-and-stability.md 14 KB
- references/ux-states.md 8.3 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.
- 15d ago Changed · +1 lines e790cfe3ecd3
- 19d ago First seen · 126 lines · 148 tokens per session scan A 1b79bbb000c8
compose-ui is a skill published in the GitHub repository Meet-Miyani/compose-skill (304 stars, last pushed 2d ago), licensed MIT. It adds 148 tokens to every session and 3,482 once invoked, about $0.0006 per session on Opus 5.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-10-02.
Other skills, from other repositories
compose-component-design
Use when designing or reviewing reusable Jetpack Compose component APIs with modifier parameters, root layout placement, caller-provided variable content, primitive content parameters, optional content, or boolean shape flags.
compose-screens-footguns
Compose screen and interaction traps: navigation, adaptive layout, window insets, pagers, toolbars, sheets, list drag and selection, sliders, text fields, settings UI, one-shot effects. Use when layout, gestures or navigation misbehave.
compose-visuals-footguns
Compose look-and-feel traps: theme and colour tokens, artwork palettes, gradients and scrims, shimmer, glass and particle effects, animation, image loading, charts and stats displays (percent changes, shares, buckets). Use when a visual bands, pops, freezes or misleads.
m3-expressive
Material 3 Expressive design patterns for Jetpack Compose - expressive theming, motion physics, shape morphing, typography emphasis, color emphasis, and all 28 expressive components.
liquid-glass
Apple Liquid Glass design patterns for SwiftUI iOS 26 - glass effects, morphing, containers, interactive glass, tinting, accessibility, and cross-platform glass design.
tipkit
In-app tips and feature discovery on iOS/macOS with Apple's TipKit — the Tip protocol (title/message/image/actions/options/id), display via TipView, popoverTip(:arrowEdge:action:), and UIKit TipUIView/TipUIPopoverViewController; eligibility with @Parameter + the #Rule macro and Event.donate(); Tips.configure…