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 RoninForge/roninforge-kotlin-compose --skill compose-new-screengit clone --depth 1 https://github.com/RoninForge/roninforge-kotlin-composeWrote 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/roninforge/roninforge-kotlin-compose/compose-new-screen)<a href="https://agentmods.dev/skills/roninforge/roninforge-kotlin-compose/compose-new-screen"><img src="https://agentmods.dev/badge/skills/roninforge/roninforge-kotlin-compose/compose-new-screen/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/roninforge/roninforge-kotlin-compose/compose-new-screen"><img src="https://agentmods.dev/badge/skills/roninforge/roninforge-kotlin-compose/compose-new-screen.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.00050 | $0.01016 |
| Opus 5.5 | $0.00020 | $0.00406 |
| Sonnet 5.5 | $0.00010 | $0.00203 |
| Haiku 4.5 | $0.00005 | $0.00102 |
Grade A, and why
compose-new-screen 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.
How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scaffold Jetpack Compose Screen
When to Use
When creating a new screen (e.g. Profile, Settings, OrderDetail) in a Compose-based Android app.
Instructions
-
Choose the route name and arguments. Define the route as a
@Serializabledata class ordata object:@Serializable data class Profile(val userId: String) -
Define the UI state as a sealed interface:
sealed interface ProfileUiState { data object Loading : ProfileUiState data class Success(val user: User) : ProfileUiState data class Error(val message: String) : ProfileUiState } -
Define intents (events from UI to ViewModel):
sealed interface ProfileIntent { data object Refresh : ProfileIntent } -
Create the ViewModel:
@HiltViewModel class ProfileViewModel @Inject constructor( private val repo: ProfileRepository, savedState: SavedStateHandle, ) : ViewModel() { private val args = savedState.toRoute<Profile>() val state: StateFlow<ProfileUiState> = repo.observeUser(args.userId) .map { ProfileUiState.Success(it) as ProfileUiState } .catch { emit(ProfileUiState.Error(it.message ?: "Unknown")) } .stateIn( scope = viewModelScope, started = SharingStarted.WhileSubscribed(5_000), initialValue = ProfileUiState.Loading, ) fun onIntent(intent: ProfileIntent) { when (intent) { ProfileIntent.Refresh -> viewModelScope.launch { repo.refresh(args.userId) } } } } -
Create the stateful Route composable (requests the VM, collects state, delegates to Screen):
@Composable fun ProfileRoute(vm: ProfileViewModel = hiltViewModel()) { val state by vm.state.collectAsStateWithLifecycle() ProfileScreen(state, onIntent = vm::onIntent) } -
Create the stateless Screen composable:
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 · 149 lines · 50 tokens per session scan A e852b2f59fde
compose-new-screen is a skill published in the GitHub repository RoninForge/roninforge-kotlin-compose (1 stars, last pushed 4mo ago), licensed MIT. It adds 50 tokens to every session and 1,016 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
compose-feature
Adds, changes, or reviews a screen, sheet, dialog, or destination slice (endpoint to repository to ViewModel to UI to navigation to DI to tests) in a Compose or CMP project. Use when adding a screen, building a new feature, adding a ViewModel or destination, wiring list/detail or a form screen, scaffolding a slice, or…
compose-platform
Owns platform splits for Compose Multiplatform apps: places declarations in commonMain, chooses expect/actual vs interface plus DI, wires host adapters and ports, and validates iOS/Swift interop, desktop and web targets, and platform lifecycle. Use when touching commonMain, expect, actual, iosMain, Swift, SKIE, Flow…
Appium Mobile Testing
Mobile application testing skill using Appium for iOS and Android, covering device capabilities, selectors, gestures, and cross-platform testing strategies.
Espresso Android Testing
Android UI testing with Espresso framework including view matchers, actions, assertions, idling resources, and RecyclerView testing patterns.
compose-architecture
Use when writing, changing or reviewing code that touches the house contract for Jetpack Compose and Compose Multiplatform apps: module graph, MVI/BaseViewModel, error tiers, state ownership, naming, Koin DI, Navigation 3 and coroutines. The compose skill is the entry point. Do NOT use for Gradle-only work…
compose-project
Owns project and build-level work for Compose and Compose Multiplatform apps: bootstrapping a new project, adopting the kit in an existing project, adding or extracting a module, convention plugins in build-logic, the version catalog, and CI plus agent hooks. Use when starting a Compose Multiplatform app, adding a…