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/preshan/GroceryListWrote 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/preshan/grocerylist/database-rules)<a href="https://agentmods.dev/rules/preshan/grocerylist/database-rules"><img src="https://agentmods.dev/badge/rules/preshan/grocerylist/database-rules/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/preshan/grocerylist/database-rules"><img src="https://agentmods.dev/badge/rules/preshan/grocerylist/database-rules.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.00211 | $0.00211 |
| Opus 5.5 | $0.00084 | $0.00084 |
| Sonnet 5.5 | $0.00042 | $0.00042 |
| Haiku 4.5 | $0.00021 | $0.00021 |
Grade A, and why
database-rules 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
Database Rules
Use Room/SQLite as the main local database.
Core tables:
categoriesstore_typesitemsshopping_sessionsshopping_session_itemsapp_settings
Optional later:
list_templateslist_template_itemsimport_logsprivacy_consents
Data rules:
- Grocery list data must remain local.
- Do not upload grocery data anywhere.
- Use soft delete with
is_active=falsefor items, categories, and store types. - Keep shopping session item snapshots so old sessions are not broken if item names change.
- CSV/text is only for export/import/share, not main storage.
- Use indexes for search and filtering.
Additional safety rules:
- Add explicit Room migrations for schema changes in release builds.
- Do not use destructive migration in production.
- Keep foreign keys for category/store/session integrity.
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 · 38 lines · 211 tokens per session scan A c44fb7a809da
database-rules is a cursor rule published in the GitHub repository preshan/GroceryList (2 stars, last pushed 5mo ago), licensed MIT. It adds 211 tokens to every session, about $0.0008 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 cursor rules, from other repositories
android-local-persistence-datastore
Persist lightweight user and app preferences with DataStore, schema-safe models, and migration-aware defaults.
android-serialization-offline-sync
Coordinate serialization, caching, conflict handling, and offline-first sync flows in Android apps.
android-room-database
Model Room entities, DAOs, transactions, migrations, schema exports, and test-safe local persistence.
105-data-model-checklist
A Chinese-language checklist for checking SwiftData data models. SwiftData is Apple’s framework for storing app data.
no-backward-compatibility
Do not add backward-compatibility shims or migration scaffolding.
postgresql
This guide defines the definitive best practices for writing clean, performant, and maintainable PostgreSQL SQL, focusing on modern conventions and avoiding common pitfalls.