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/ashtanko/compose-android-template/compose-animationsnpx skills add ashtanko/compose-android-template --skill compose-animationsgit clone --depth 1 https://github.com/ashtanko/compose-android-templateWrote 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/ashtanko/compose-android-template/compose-animations)<a href="https://agentmods.dev/skills/ashtanko/compose-android-template/compose-animations"><img src="https://agentmods.dev/badge/skills/ashtanko/compose-android-template/compose-animations.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 | $0.00064 | $0.02516 |
| Opus 5 | $0.00032 | $0.01258 |
| Sonnet 5 | $0.00013 | $0.00503 |
| Haiku 4.5 | $0.00006 | $0.00252 |
Grade A, and why
compose-animations 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 3d 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Compose: animations
Core principle
Pick the smallest API that matches the problem: built-in visibility and layout transitions first, then a single animated value, then a shared transition object when several values must move together, then gesture-level or imperative APIs when the framework cannot express the motion.
Review procedure
- Identify the visual job: show/hide, one value, coordinated values, content swap, size change, or gesture-driven motion.
- Choose the smallest API from the table below.
- Check lifecycle semantics: should hidden content leave composition, keep focus/state, or only become transparent?
- Check identity: for state-holder wrappers, choose
AnimatedContent.contentKeyby visual shape rather than payload churn. - Check performance: keep frame-rate animation values as
Stateand read them in layout/draw block modifiers when possible. - Escalate to
Animatableor lower-level APIs only when target-state animation cannot express the motion.
Pick the smallest animation API
| Need | API |
|---|---|
| Show or hide a subtree with enter/exit semantics; content is removed after exit completes | AnimatedVisibility |
| Animate one property toward a target derived from state | animateFloatAsState / animateDpAsState / animateColorAsState / animateOffsetAsState / … |
| Several animated values keyed off one boolean, enum, or sealed state | rememberTransition + transition child animations (animateFloat, animateDp, animateColor, animateValue, …) |
| Smooth size when child layout height/width changes (e.g. text wraps) | Modifier.animateContentSize() |
| Swap between different composable trees for the same slot | AnimatedContent or Crossfade |
| User-driven motion (drag, fling, interruptible springs) | Animatable and related coroutine APIs (see Advanced pointers) |
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.
- 3d ago First seen · 194 lines · 64 tokens per session scan A 037c584fae41
compose-animations is a skill published in the GitHub repository ashtanko/compose-android-template (10 stars, last pushed 6d ago), licensed MIT. It adds 64 tokens to every session and 2,516 once invoked, about $0.0003 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-31.
Other skills, from other repositories
sceneview
Build 3D and AR apps with the SceneView SDK in Jetpack Compose, SwiftUI (iOS/macOS/visionOS via SceneViewSwift), Web (Filament.js), Flutter and React Native. Use whenever the user asks for "3D in Compose", "AR with ARCore in Compose", a model viewer, or any cross-platform 3D/AR app where the dependency is…
sceneview-ios
Build 3D and AR apps on Apple platforms (iOS, macOS, visionOS) with SceneViewSwift — the SwiftUI wrapper around RealityKit. Use whenever the user asks for "3D in SwiftUI", "AR with ARKit in SwiftUI", a model viewer for iOS, or any Apple-platform 3D/AR app where the dependency is the SceneViewSwift Swift Package from…
kotlin-control-flow
Use when writing or reviewing Kotlin branching and control flow: when expressions, guard conditions, sealed type exhaustiveness, smart casts, nullable branching, early returns, or replacing complex if/else chains.
using-chrisbanes-skills
Use when debugging, benchmarking, or profiling leads into Kotlin or Jetpack Compose source before the cause is known, or when one task spans multiple Kotlin or Compose concerns, especially plain Kotlin Flow or navigation delivery plus sealed branching.
kotlin-api-design
Use when designing or reviewing Kotlin function ownership, member or extension functions, factories, single-field domain types, value classes, data classes, Kotlin Multiplatform expect/actual declarations, or platform service boundaries.
kotlin-concurrency-and-flow
Use when writing or reviewing Kotlin coroutine scope ownership, raw Thread or Executor work, init launches, non-suspending launch APIs, runBlocking, cancellation, StateFlow, SharedFlow, Channel, stateIn, SharingStarted, state updates, or one-shot events.