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/HeeGyeong/ComposeSampleWrote 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/heegyeong/composesample/code-style)<a href="https://agentmods.dev/rules/heegyeong/composesample/code-style"><img src="https://agentmods.dev/badge/rules/heegyeong/composesample/code-style/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/heegyeong/composesample/code-style"><img src="https://agentmods.dev/badge/rules/heegyeong/composesample/code-style.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.00415 |
| Opus 5.5 | $0.00000 | $0.00166 |
| Sonnet 5.5 | $0.00000 | $0.00083 |
| Haiku 4.5 | $0.00000 | $0.00042 |
Grade A, and why
code-style 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
description: "Kotlin & Jetpack Compose Code Style Guide with Korean comments" globs: "" alwaysApply: true
Kotlin & Jetpack Compose Code Style Guide
Overview
This rule defines comprehensive code style guidelines for Kotlin and Jetpack Compose development. References CreateUICodeSnippet.md.
Technical Specifications
- Language: Kotlin
- Framework: Jetpack Compose
- Architecture: MVVM + Clean Architecture
- Comments: Write in Korean
- File Coverage: Write all parts without omission
Naming Conventions
- Classes: PascalCase
- Functions: camelCase
- Variables: camelCase
- Constants: SCREAMING_SNAKE_CASE
- Composable Functions: PascalCase
Composable Function Rules
- Must include Preview functions
- Parameters must have explicit default values
- Apply state hoisting
- Reusable components should be in separate files
Code Formatting
- Indentation: 4 spaces
- Maximum line length: 120 characters
- Maximum function length: 50 lines
- Maximum file length: 500 lines
Comment Rules
- Comments only for complex business logic
- Use KDoc format
- TODO comments must include resolution deadline
Code Style Examples
Color and Style Usage
Text(
modifier = Modifier,
text = title,
color = Color.LightGray,
style = getTextStyle(12)
)
ViewModel Usage
- Reference DIRules.md
- Use Koin as DI framework
Implementation Guidelines
- Implement UI that matches provided designs/requirements
- Maintain build integrity using dummy data
- Express full context of requirements
- Base implementation on comprehensive understanding
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 · 69 lines · 0 tokens per session scan A 93b008793246
code-style is a cursor rule published in the GitHub repository HeeGyeong/ComposeSample (11 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 415 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
kotlin-springboot-rules
A set of coding rules for Kotlin applications built with Spring Boot, a Java-based framework for web services. It covers project layout, naming, Kotlin style, and common design patterns.
gradle
Enforce modern Gradle build practices for Java and Android projects, focusing on Kotlin DSL, modularity, version catalogs, and performance optimizations.
android-viewmodel
Android ViewModel conventions — StateFlow, repository abstraction, coroutines, no LiveData.
trove-swift
Swift 6 and SwiftUI coding conventions for iOS development. Auto-activates when working with Swift files. Covers @Observable, async/await, NavigationStack, Swift Testing, and accessibility.
shared-module
KMP shared module constraints — no platform imports in domain/, expect/actual conventions, pure Kotlin business logic.
swift-argument-parser
Documentation and usage patterns for Swift Argument Parser for command-line tools.