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/project-structure)<a href="https://agentmods.dev/rules/heegyeong/composesample/project-structure"><img src="https://agentmods.dev/badge/rules/heegyeong/composesample/project-structure/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/project-structure"><img src="https://agentmods.dev/badge/rules/heegyeong/composesample/project-structure.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.00190 |
| Opus 5.5 | $0.00000 | $0.00076 |
| Sonnet 5.5 | $0.00000 | $0.00038 |
| Haiku 4.5 | $0.00000 | $0.00019 |
Grade A, and why
project-structure 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
Project Structure Guide
Layer Structure
app/
├── domain/
│ ├── model/
│ ├── repository/
│ └── usecase/
├── data/
│ ├── remote/
│ ├── local/
│ └── repository/
└── presentation/
├── ui/
├── viewmodel/
└── navigation/
Modularization Rules
- Separate modules by feature
- Common utilities in core module
- UI components in design-system module
Dependency Rules
- Domain layer uses pure Kotlin only
- Data layer depends on domain layer
- Presentation layer depends only on domain layer
Resource Management
- Strings in strings.xml
- Colors in colors.xml
- Themes in theme.xml
- Images in drawable/ or mipmap/
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 · 40 lines · 0 tokens per session scan A 564affc5ebe2
project-structure is a cursor rule published in the GitHub repository HeeGyeong/ComposeSample (11 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 190 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
nativescript
NativeScript best practices and patterns for mobile applications.
cursorrules
Kortix is a React Native + Expo app built with TypeScript, NativeWind (Tailwind CSS), and a custom design system.
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.
ios-ui-development-focus
UI/UX and SwiftUI best practices - HIG compliance, presentation APIs, layout patterns.
uts
A set of coding rules for UTS, a strongly typed language used by uni-app x to build apps for multiple platforms.