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/sampaio-tech/flutter-core-modulesWrote 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/sampaio-tech/flutter-core-modules/feature-locale)<a href="https://agentmods.dev/rules/sampaio-tech/flutter-core-modules/feature-locale"><img src="https://agentmods.dev/badge/rules/sampaio-tech/flutter-core-modules/feature-locale/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/sampaio-tech/flutter-core-modules/feature-locale"><img src="https://agentmods.dev/badge/rules/sampaio-tech/flutter-core-modules/feature-locale.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.00786 |
| Opus 5.5 | $0.00000 | $0.00314 |
| Sonnet 5.5 | $0.00000 | $0.00157 |
| Haiku 4.5 | $0.00000 | $0.00079 |
Grade A, and why
feature-locale 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 2mo 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature: Locale — Rules
What Is Already Implemented — Check Before Building
| Capability | Status |
|---|---|
| Persist locale to SharedPreferences | ✅ SetLocaleUsecase — do NOT reimplement |
| Read persisted locale (sync) | ✅ GetLocaleUsecase — do NOT reimplement |
| Remove persisted locale (reset to system) | ✅ RemoveLocaleUsecase — do NOT reimplement |
| Debug/prod key separation | ✅ DatabaseKeys.locale — automatic |
Reactive locale StateNotifier |
❌ Not in package — implement in consuming app following ThemeStateNotifier pattern |
| Locale picker UI | ❌ Not in package — implement in consuming app |
Before adding locale-related code, check if the above use cases already satisfy the requirement.
Layer Structure
lib/src/features/locale/
├── domain/
│ ├── repositories/locale_repository.dart # abstract LocaleRepository
│ └── usecases/
│ ├── get_locale_usecase.dart
│ ├── set_locale_usecase.dart
│ └── remove_locale_usecase.dart
└── data/
└── repositories/locale_repository.dart # LocaleRepositoryImpl + provider
There is no presentation/ layer — locale has no UI in this package.
Correct Usage Patterns
Reading locale on app start (sync)
// Read once; null means user has not selected a locale (use system locale)
final savedLocale = ref.read(getLocaleUsecaseProvider)(); // Locale?
Persisting a locale change
final setLocale = ref.read(setLocaleUsecaseProvider);
await setLocale(locale: const Locale('pt', 'BR'));
Resetting to system locale
await ref.read(removeLocaleUsecaseProvider)();
Wiring into CupertinoApp / MaterialApp
CupertinoApp(
locale: savedLocale, // null = let the OS decide
supportedLocales: const [Locale('en'), Locale('pt', 'BR')],
localizationsDelegates: const [...],
)
Reactive locale (consuming app, not this package)
Follow the ThemeStateNotifier pattern — create a LocaleStateNotifier extends SafeStateNotifier<Locale?> in the consuming app that wraps the use cases.
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.
- 2mo ago First seen · 95 lines · 0 tokens per session scan A 32607c2d7d5a
feature-locale is a cursor rule published in the GitHub repository sampaio-tech/flutter-core-modules (2 stars, last pushed 16d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 786 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
internationalization
A set of rules for internationalization, the practice of adapting an application for multiple languages and regions. It covers file structure, translation namespaces, and using translations in components.
cmd-moodle-mustache-lint
Lint Mustache templates for accessibility, security, hard-coded strings, and Moodle template conventions. (invoke by typing: @moodle-mustache-lint).
chinese-language
A language rule that requires replies, comments, and commit messages to use Simplified Chinese unless another language is requested.
rtl-right-to-left-i18n-cursorrules-prompt-file
Cursor rule "rtl-right-to-left-i18n-cursorrules-prompt-file" from XD3an/awesome-ai-coding-all-in-one, covering rtl (right-to-left) development rules, core rules, 1. logical css properties, 2. tailwind css logical classes and 3. react native logical properties.
uninettuno-monografia
Regole UNINETTUNO per tesi TRIENNALE in italiano, con termini tecnici inglesi ammessi.
report
A set of rules for generating HTML dashboards that present data and analysis in Korean. It defines the required page structure, visual libraries, fonts, and report content.