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/naming-conventions)<a href="https://agentmods.dev/rules/sampaio-tech/flutter-core-modules/naming-conventions"><img src="https://agentmods.dev/badge/rules/sampaio-tech/flutter-core-modules/naming-conventions/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/naming-conventions"><img src="https://agentmods.dev/badge/rules/sampaio-tech/flutter-core-modules/naming-conventions.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.01519 | $0.01519 |
| Opus 5.5 | $0.00608 | $0.00608 |
| Sonnet 5.5 | $0.00304 | $0.00304 |
| Haiku 4.5 | $0.00152 | $0.00152 |
Grade A, and why
naming-conventions 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 — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Naming Conventions — flutter_core_modules
Files — snake_case with semantic suffix
| Suffix | Use for |
|---|---|
*_usecase.dart |
Domain use case class |
*_state_notifier.dart |
StateNotifier subclass |
*_repository.dart |
Repository (abstract or concrete, in their own directories) |
*_data_source.dart |
DataSource (abstract or concrete) |
*_widget.dart |
Widget class |
*_failure.dart |
Sealed failure class |
| no suffix | Hooks, utils, config (safe_effect.dart, revenue_cat.dart) |
Use Cases — {Verb}{Entity}Usecase
Always verb-first. Allowed verbs:
| Verb | Example |
|---|---|
Get |
GetThemeDataUsecase, GetLocaleUsecase, GetDownloadUrlUsecase |
Set |
SetThemeDataUsecase, SetLocaleUsecase |
Remove |
RemoveThemeDataUsecase, RemoveLocaleUsecase |
Sync |
SyncPurchasesUsecase |
Invalidate |
InvalidateCustomerInfoCacheUsecase |
Add / Remove |
AddCustomerInfoUpdateListenerUsecase |
Track |
TrackEventUsecase |
Is |
IsAvailableUsecase |
Request |
RequestReviewUsecase |
Open |
OpenStoreListingUsecase |
State Notifiers — {Feature}StateNotifier
ThemeStateNotifier
HapticFeedbackStateNotifier
CustomerInfoStateNotifier
GetDownloadUrlStateNotifier
InAppReviewStateNotifier
The provider variable mirrors the class name: themeStateNotifierProvider, customerInfoStateNotifierProvider.
Providers — camelCase + Provider suffix
// Use cases:
getThemeDataUsecaseProvider
setThemeDataUsecaseProvider
getDownloadUrlUsecaseProvider
// Notifiers:
themeStateNotifierProvider
hapticFeedbackStateNotifierProvider
getDownloadUrlStateNotifierProvider // family
// Repositories / data sources:
themeRepositoryProvider
firebaseStorageRepositoryProvider
sharedPreferencesCacheLocalDataSourceProvider
// Derived / computed:
isPremiumCustomerProvider
navigatiorKeyProvider // NOTE: "navigatior" spelling is intentional — do not rename
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 · 214 lines · 1,519 tokens per session scan A 5251d40c67f3
naming-conventions is a cursor rule published in the GitHub repository sampaio-tech/flutter-core-modules (2 stars, last pushed 16d ago), licensed MIT. It adds 1,519 tokens to every session, about $0.0061 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
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.