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-featuregit 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-feature)<a href="https://agentmods.dev/skills/meet-miyani/compose-skill/compose-feature"><img src="https://agentmods.dev/badge/skills/meet-miyani/compose-skill/compose-feature/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-feature"><img src="https://agentmods.dev/badge/skills/meet-miyani/compose-skill/compose-feature.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.00150 | $0.03438 |
| Opus 5.5 | $0.00060 | $0.01375 |
| Sonnet 5.5 | $0.00030 | $0.00688 |
| Haiku 4.5 | $0.00015 | $0.00344 |
Grade A, and why
compose-feature 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 22d 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Compose Feature
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 build one slice end to end and you refuse to ship it unfinished. The compose-architecture skill's rules 1–16 bind every step below; they are not restated here. 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 helper, component, token, and file 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 code, 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 |
| Write or review composables, lists, motion, accessibility, tokens, resources | the compose-ui skill |
| Write or review repositories, Ktor, Room, DataStore, Paging, offline-first | the compose-data skill |
| New project or module, convention plugins, version catalog, CI, hooks | the compose-project skill |
commonMain sharing, expect/actual, iOS/Swift, desktop, web |
the compose-platform skill |
Non-negotiables
What ships with it
23 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.
- examples.md 8.5 KB
- references/review-mode.md 8.0 KB
- references/testing.md 13 KB
- references/ui-testing.md 4.4 KB
- scripts/new-feature.sh 7.6 KB runs code
- templates/feature/build.gradle.kts 1.8 KB
- templates/feature/commonTest/__Name__ViewModelTest.kt 9.8 KB
- templates/feature/commonTest/Fake__Name__Repository.kt 2.0 KB
- templates/feature/data/remote/__Item__Dto.kt 543 B
- templates/feature/data/remote/__Name__RemoteDataSource.kt 1.3 KB
- templates/feature/data/remote/mapper/__Item__DtoMapper.kt 896 B
- templates/feature/data/repository/Default__Name__Repository.kt 1.2 KB
- templates/feature/di/__Name__FeatureModule.kt 688 B
- templates/feature/domain/model/__Item__.kt 513 B
- templates/feature/domain/repository/__Name__Repository.kt 726 B
- templates/feature/navigation/__Name__NavKey.kt 952 B
- templates/feature/presentation/__name__/__Name__Contract.kt 1.3 KB
- templates/feature/presentation/__name__/__Name__Route.kt 1.6 KB
- templates/feature/presentation/__name__/__Name__Screen.kt 2.0 KB
- templates/feature/presentation/__name__/__Name__ViewModel.kt 3.4 KB
- templates/feature/presentation/__name__/mapper/__Item__UiMapper.kt 899 B
- templates/feature/presentation/__name__/model/__Item__UiModel.kt 567 B
- templates/feature/README.md 2.0 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.
- 22d ago Changed · +1 lines a9c405343f7f
- 26d ago First seen · 158 lines · 150 tokens per session scan A 223e8abdf286
compose-feature is a skill published in the GitHub repository Meet-Miyani/compose-skill (306 stars, last pushed 5d ago), licensed MIT. It adds 150 tokens to every session and 3,438 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-animations
Use when writing or reviewing Jetpack Compose motion: visibility enter/exit, animating one property toward a target, color or size transitions, multiple properties from one state, switching composable content, or choosing between AnimatedVisibility, animateAsState, rememberTransition, AnimatedContent, and Crossfade.
compose-focus-navigation
Use when writing or reviewing Jetpack Compose UI for TV, keyboard, desktop, accessibility focus, D-pad navigation, FocusRequester, focusProperties, key events, or initial focus behavior.
compose-state-and-effects
Use when writing or reviewing Jetpack Compose state ownership, remember state, state hoisting, screen state holders, LaunchedEffect, DisposableEffect, SideEffect, Flow collection, navigation, snackbar, analytics, or focus requests.
android-benchmark-comparison
Use when comparing physical Android benchmark configurations, investigating inconsistent rankings, or selecting an Android default from measured results. Do not use for code-level Compose performance diagnosis without a configuration comparison.
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-performance
Use when investigating Jetpack Compose recomposition cost, compiler stability reports, skippability, unstable parameters, frame-rate State reads, cross-phase snapshot back-writing, or @ReadOnlyComposable contracts.