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.
git clone --depth 1 https://github.com/baijum/ukulele-companionWrote 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/rules/baijum/ukulele-companion/compose-coroutines)<a href="https://agentmods.dev/rules/baijum/ukulele-companion/compose-coroutines"><img src="https://agentmods.dev/badge/rules/baijum/ukulele-companion/compose-coroutines/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/rules/baijum/ukulele-companion/compose-coroutines"><img src="https://agentmods.dev/badge/rules/baijum/ukulele-companion/compose-coroutines.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.00000 | $0.00543 |
| Opus 5.5 | $0.00000 | $0.00217 |
| Sonnet 5.5 | $0.00000 | $0.00109 |
| Haiku 4.5 | $0.00000 | $0.00054 |
Grade A, and why
compose-coroutines 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 1mo 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.
What it actually says
-
Guard programmatic scroll from state observers
scrollState.isScrollInProgresscannot distinguish between a user finger drag and a programmaticanimateScrollTocall. If you observeisScrollInProgressto detect manual scrolling, always gate it with a flag:val programmaticScroll = remember { mutableStateOf(false) } // Auto-scroll loop LaunchedEffect(autoScrolling) { if (autoScrolling) { while (autoScrolling) { programmaticScroll.value = true try { scrollState.animateScrollTo(/* ... */) } finally { programmaticScroll.value = false } delay(16L) } } } // Manual-scroll detector — skip when programmatic LaunchedEffect(scrollState.isScrollInProgress) { if (scrollState.isScrollInProgress && autoScrolling && !programmaticScroll.value) { autoScrolling = false } } -
Always wrap cancellable suspend calls in try/finally
animateScrollTo,animateTo, and similar Compose suspend functions are cancellable. If you set a flag before calling them, reset it in afinallyblock so the flag is cleared even if the coroutine is cancelled (e.g., by user touch orLaunchedEffectrecomposition):// ✅ DO flag.value = true try { scrollState.animateScrollTo(target) } finally { flag.value = false } // ❌ DON'T — flag stays true if animateScrollTo is cancelled flag.value = true scrollState.animateScrollTo(target) flag.value = false -
Prefer snapshotFlow over LaunchedEffect(stateValue) for contextual reactions
LaunchedEffect(stateValue)restarts wheneverstateValuechanges, but you lose the previous value. When you need to compare old vs. new, or combine the state change with other conditions, usesnapshotFlow:// ✅ Richer context — can debounce, filter, combine LaunchedEffect(Unit) { snapshotFlow { scrollState.isScrollInProgress } .filter { it && !programmaticScroll.value } .collect { autoScrolling = false } }
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.
- 1mo ago First seen · 68 lines · 0 tokens per session scan A 335dfdb3112f
compose-coroutines is a cursor rule published in the GitHub repository baijum/ukulele-companion (14 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 543 tokens. 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 cursor rules, from other repositories
20-android-kotlin
There is no Android SDK/NDK available in most sandboxed dev environments (including the one this codebase was originally scaffolded in). Kotlin code in this repo has generally not been compiled or run by an AI agent — only reviewed for logical consistency. Treat Kotlin changes as higher-risk than Rust changes until a…
project
Redface 2 project rules — imports AGENTS.md as source of truth.
cursorrules
You are a senior Android developer. Follow these rules strictly when writing or modifying Android/Kotlin code.
android_general_rules
For every Kotlin Android code you generate or refactor.
compose-architecture
Android architecture patterns: feature modularization, repository + data source pattern, sealed interfaces for UI state, ViewModel + StateFlow, Ktor / Retrofit + Kotlin Serialization, Room with Flow returns + KSP, coroutines structured concurrency.
android_workmanager_best_practices
Best practices for WorkManager usage in background tasks.