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/RanaNadeemAslam/android-ai-skillsWrote 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/rananadeemaslam/android-ai-skills/data-layer)<a href="https://agentmods.dev/rules/rananadeemaslam/android-ai-skills/data-layer"><img src="https://agentmods.dev/badge/rules/rananadeemaslam/android-ai-skills/data-layer/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/rananadeemaslam/android-ai-skills/data-layer"><img src="https://agentmods.dev/badge/rules/rananadeemaslam/android-ai-skills/data-layer.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.02087 |
| Opus 5.5 | $0.00000 | $0.00835 |
| Sonnet 5.5 | $0.00000 | $0.00417 |
| Haiku 4.5 | $0.00000 | $0.00209 |
Grade A, and why
data-layer 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 — 299 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert in Android data layer architecture. Follow offline-first principles, use Room for persistence, DataStore for preferences, and maintain strict layer separation with dedicated models per layer.
Repository Pattern
Source: https://developer.android.com/topic/architecture/data-layer
DO:
- Repository is the single entry point to all data for a given type:
class ArticleRepository @Inject constructor(
private val articleRemoteDataSource: ArticleRemoteDataSource,
private val articleLocalDataSource: ArticleLocalDataSource,
) {
fun getArticles(): Flow<List<Article>> =
articleLocalDataSource.observeArticles()
.map { entities -> entities.map { it.toArticle() } }
suspend fun refreshArticles() {
val networkArticles = articleRemoteDataSource.fetchArticles()
articleLocalDataSource.upsertArticles(networkArticles.map { it.toEntity() })
}
}
- Expose
Flow<T>for data that changes over time - Expose
suspendfunctions for one-shot operations - Return immutable types only
- One repository per data type (
UserRepository,ArticleRepository)
DON'T:
- Expose DataSource classes outside the data layer
- Return mutable collections (
MutableList,MutableMap) - Create a single repository for the entire app
- Put UI formatting logic in repositories
Model Separation
Source: https://developer.android.com/topic/architecture/data-layer
DO:
- Create separate model classes for each layer boundary:
// Network layer — matches API JSON
@Serializable
data class NetworkArticle(
@SerialName("article_id") val id: String,
val title: String,
@SerialName("body_text") val body: String,
@SerialName("created_at") val createdAt: String,
)
// Database layer — matches Room schema
@Entity(tableName = "articles")
data class ArticleEntity(
@PrimaryKey val id: String,
val title: String,
val body: String,
val createdAt: Long,
val lastRefreshed: Long = System.currentTimeMillis(),
)
// Domain/UI layer — what the app works with
data class Article(
val id: String,
val title: String,
val body: String,
val createdAt: Instant,
)
- Create extension functions for mapping between layers:
fun NetworkArticle.toEntity() = ArticleEntity(...)
fun ArticleEntity.toArticle() = Article(...)
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 · 299 lines · 0 tokens per session scan A a810b76b18f7
data-layer is a cursor rule published in the GitHub repository RanaNadeemAslam/android-ai-skills (6 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,087 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-31.
Other cursor rules, from other repositories
kotlin
Android finance precision, RTL/i18n, and Kotlin AI skill rules.
enterprise-design
Produce a comprehensive technical blueprint for a web product or SaaS, suitable for implementation in Figma Make, engineering sprints, an...
docs
You are a documentation engineer.
techdebt
Find and eliminate technical debt across the whole codebase — duplicated code, dead code, redundant abstractions.
swiftui-accessibility
SwiftUI accessibility rules for VoiceOver — labels, hints, traits, values, and attribute preservation.
android-gradle-build-logic
Shape Android build logic with Gradle, version catalogs, plugins, convention patterns, and toolchain compatibility.