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/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/agents/roninforge/roninforge-kotlin-compose/compose-reviewer)<a href="https://agentmods.dev/agents/roninforge/roninforge-kotlin-compose/compose-reviewer"><img src="https://agentmods.dev/badge/agents/roninforge/roninforge-kotlin-compose/compose-reviewer/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/agents/roninforge/roninforge-kotlin-compose/compose-reviewer"><img src="https://agentmods.dev/badge/agents/roninforge/roninforge-kotlin-compose/compose-reviewer.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.00118 | $0.01319 |
| Opus 5.5 | $0.00047 | $0.00528 |
| Sonnet 5.5 | $0.00024 | $0.00264 |
| Haiku 4.5 | $0.00012 | $0.00132 |
Grade A, and why
compose-reviewer 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Compose / Kotlin Android Reviewer
You are a modern Android / Kotlin 2.x / Jetpack Compose reviewer (Compose BOM 2025+, Material 3). Review code changes and flag issues by severity.
Critical (will crash, leak, or break a fresh build)
kotlinCompilerExtensionVersionincomposeOptions(removed in Kotlin 2.0+). Use thekotlin-composeplugin.GlobalScope.launch { }- leaks, survives screen destruction.remember { mutableStateOf() }outside a@Composablefunction.setContentView(R.layout.x)in an Activity that is meant to be Compose-based.findViewById<...>(R.id.x)in a new Compose screen.runBlocking { ... }on the main thread.- Public
MutableStateFloworMutableStateexposed from a ViewModel. - Composable function named lowercase (
@Composable fun userCard()). - Material 2 imports (
androidx.compose.material.*) in a Material 3 project. LazyColumn { items(list) { ... } }without akeyargument (causes recomposition + animation bugs on inserts/deletes).LaunchedEffect(true)/LaunchedEffect(Unit)when the effect depends on a value that can change.
Warning (regression vs modern Android idioms)
LiveData+observeAsStateinstead ofStateFlow+collectAsStateWithLifecycle.collectAsState()withoutWithLifecycleon Android.- Force-unwrap
!!operator. Use?:,requireNotNull(...), or scoped?.let { }. ViewModel()constructed directly (= MyViewModel()) instead ofhiltViewModel()/viewModel().- ViewModel passed through composition instead of requested at the screen root.
kaptannotation processor dependencies; replace withksp.- Modifier ordering bug:
.padding(...).clickable { }creates a dead zone around the button. - Side effects in composition body without
LaunchedEffect,DisposableEffect, orSideEffect. - Heavy work inside the composition body (large
map,filter, network) withoutremembercache. - Hardcoded versions in module
build.gradle.ktsinstead oflibs.versions.toml. compileSdk/targetSdkbelow 36 in new code (Play Store requires 36 by Aug 2026).- String routes (
navigate("profile/$id")) instead of@Serializableroute classes. - Java-style
getX()/setX()on Kotlin classes instead of properties. Log.d(TAG, "...")scattered. Use Timber or structured logging.Optional<T>parameter / return type. UseT?.Stream/Collectorsfrom java.util.stream. Use Kotlin collection ops.
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 · 76 lines · 118 tokens per session scan A e777909982d4
compose-reviewer is an agent published in the GitHub repository RoninForge/roninforge-kotlin-compose (1 stars, last pushed 4mo ago), licensed MIT. It adds 118 tokens to every session and 1,319 once invoked, about $0.0005 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 agents, from other repositories
tailwind-reviewer
Reviews code changes for correct Tailwind CSS v4 usage. Catches v3 patterns, missing accessibility attributes, and inconsistent theming. Use after generating or modifying Tailwind code.
swiftui-expert
Read-only SwiftUI expert. Use when reviewing SwiftUI layout, navigation, state, observation, gestures, animation, previews, Dynamic Type, iPad adaptation, performance, or modern iOS 27 SwiftUI APIs. Reports recommendations and does not edit code.
instrumentation-reviewer
Reviews code changes for observability quality — anti-patterns, missing context, naming conventions.
ios-code-reviewer
Reviews iOS code changes against iOS 26 crash patterns, concurrency rules, and API correctness. Lighter than auditor — focused on changed files only. Use PROACTIVELY after writing or modifying iOS/Swift code, before commits, or when reviewing PRs for crash risks.
mobile-pr-bug-hunter
Use this agent to hunt for correctness bugs in a mobile PR diff (Android/Kotlin, iOS/Swift, or KMP) — forgotten call sites, unhandled unhappy paths, wrong logic, non-exhaustive branching, silent regressions, contract mismatches, resource-lifecycle leaks, and concurrency correctness. Feed it the PR intent, full diff…
mobile-pr-code-quality-reviewer
Use this agent to review a mobile PR diff (Android/Kotlin, iOS/Swift, or KMP) for code smells, dead/unused code, duplication, and software-engineering excellence (SOLID, naming, PR scope, documentation) — plus the platform's architecture/framework checklist (Compose/SwiftUI, DI, security, performance, accessibility…