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 rules/roninforge/roninforge-kotlin-compose/compose-testinggit clone --depth 1 https://github.com/RoninForge/roninforge-kotlin-composeWhat 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.00045 | $0.01661 |
| Opus 5 | $0.00023 | $0.00830 |
| Sonnet 5 | $0.00009 | $0.00332 |
| Haiku 4.5 | $0.00005 | $0.00166 |
Grade A, and why
compose-testing 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 yesterday.
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 — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Compose / Kotlin Android Testing
Compose UI tests
class ProfileScreenTest {
@get:Rule
val rule = createComposeRule()
@Test
fun showsLoading() {
rule.setContent {
AppTheme { ProfileScreen(ProfileUiState.Loading, onIntent = {}) }
}
rule.onNodeWithContentDescription("Loading").assertIsDisplayed()
}
@Test
fun showsUserName_onSuccess() {
val user = User("alice", "Alice", "[email protected]")
rule.setContent {
AppTheme { ProfileScreen(ProfileUiState.Success(user), onIntent = {}) }
}
rule.onNodeWithText("Alice").assertIsDisplayed()
rule.onNodeWithText("[email protected]").assertIsDisplayed()
}
@Test
fun invokesOnIntent_whenButtonClicked() {
val user = User("alice", "Alice", "[email protected]")
var intent: ProfileIntent? = null
rule.setContent {
AppTheme {
ProfileScreen(ProfileUiState.Success(user), onIntent = { intent = it })
}
}
rule.onNodeWithText("Refresh").performClick()
assertEquals(ProfileIntent.Refresh, intent)
}
}
Test the stateless Screen composable. It takes state and lambdas, so the test never needs a ViewModel.
Semantic matchers
Prefer semantic queries over node-tree introspection:
onNodeWithText("Alice")- visible text content.onNodeWithContentDescription("Profile avatar")- for icons/images.onNodeWithTag("submit-button")- viaModifier.testTag(...)(use sparingly; tags are not visible to users).onAllNodesWithText(...)- when multiple nodes match.
Custom matchers:
rule.onNode(hasText("Save") and hasClickAction()).performClick()
ViewModel tests with runTest + Turbine
class ProfileViewModelTest {
@get:Rule
val mainDispatcherRule = MainDispatcherRule() // sets Dispatchers.Main to a test dispatcher
@Test
fun emitsSuccess_whenRepoReturnsUser() = runTest {
val user = User("alice", "Alice", "[email protected]")
val repo = FakeProfileRepository(user = user)
// Build the route's SavedStateHandle via navigation-testing so toRoute<Profile>() works.
val savedState = Profile("alice").let {
SavedStateHandle().apply { set("userId", "alice") } // see note below
}
val vm = ProfileViewModel(repo, savedState)
vm.state.test {
assertEquals(ProfileUiState.Loading, awaitItem())
val item = awaitItem()
assertTrue(item is ProfileUiState.Success)
assertEquals("Alice", (item as ProfileUiState.Success).user.name)
cancelAndIgnoreRemainingEvents()
}
}
}
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.
- yesterday First seen · 204 lines · 45 tokens per session scan A cc402d814d69
compose-testing is a cursor rule published in the GitHub repository RoninForge/roninforge-kotlin-compose (1 stars, last pushed 2mo ago), licensed MIT. It adds 45 tokens to every session and 1,661 once invoked, about $0.0002 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 cursor rules, from other repositories
tailwind-v4-core
Core Tailwind CSS v4 rules. Enforces correct v4 syntax and prevents common v3 fallbacks. Attach to all conversations involving Tailwind CSS.
tailwind-v4-migration
Tailwind CSS v3-to-v4 migration rules. Activated when the agent determines migration work is needed. Covers step-by-step upgrade process, common pitfalls, and automated migration tooling.
tailwind-v4-utilities
Tailwind CSS v4 utility class rules for template and markup files. Covers renamed classes, new utilities, container queries, gradients, and accessibility patterns.
tailwind-v4-anti-patterns
Tailwind CSS v4 anti-pattern detection. Prevents the most common AI-generated mistakes: version mixing, deprecated config patterns, and removed utilities.
tailwind-v4-config
Tailwind CSS v4 configuration rules for CSS and build tool files. Covers @theme, @source, @import, PostCSS, and Vite plugin setup.
android-project
Core behavior rules for AI agents working on this Android project.