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-settings)<a href="https://agentmods.dev/rules/sampaio-tech/flutter-core-modules/feature-settings"><img src="https://agentmods.dev/badge/rules/sampaio-tech/flutter-core-modules/feature-settings/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-settings"><img src="https://agentmods.dev/badge/rules/sampaio-tech/flutter-core-modules/feature-settings.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.01335 |
| Opus 5.5 | $0.00000 | $0.00534 |
| Sonnet 5.5 | $0.00000 | $0.00267 |
| Haiku 4.5 | $0.00000 | $0.00134 |
Grade A, and why
feature-settings 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature: Settings — Rules
What Is Already Implemented — Check Before Building
| Capability | Status |
|---|---|
| Haptic feedback toggle (persisted) | ✅ hapticFeedbackStateNotifierProvider |
| Prevent screen sleep / wakelock (persisted) | ✅ wakelockStateNotifierProvider |
| Generic toggle row widget (not persisted) | ✅ SwitchRowWidget |
Toggle wired to any CacheBoolStateNotifier |
✅ CacheBoolRowWidget |
| Dark / Light mode toggle row | ✅ ThemeRowWidget |
| Auto-haptic on list row tap | ✅ Built into LabelRowWidget.copyToClipboard / openLink |
| Notification permission settings | ❌ Not in package — use app_settings package |
| Non-boolean persisted setting | ❌ Not in package — implement following ThemeStateNotifier pattern |
Before creating a new settings notifier or widget, verify whether the above already satisfies the requirement.
Layer Structure
lib/src/features/settings/
└── presentation/
├── notifiers/
│ ├── haptic_feedback_state_notifier.dart
│ └── wakelock_state_notifier.dart
└── widgets/
├── switch_row_widget.dart
├── cache_bool_row_widget.dart
└── theme_row_widget.dart
There is no domain or data layer — settings use the core CacheBoolStateNotifier directly.
Adding a New Boolean Setting
Extend CacheBoolStateNotifier with a unique key and default value:
class MyFeatureStateNotifier extends CacheBoolStateNotifier {
MyFeatureStateNotifier({required super.getBoolUsecase, required super.setBoolUsecase, required super.removeCacheUsecase})
: super(key: myFeatureKey(), defaultValue: true);
}
const _key = 'myFeature';
String myFeatureKey() => kDebugMode ? '${_key}Debug' : _key;
final myFeatureStateNotifierProvider =
StateNotifierProvider<MyFeatureStateNotifier, bool>(
(ref) => MyFeatureStateNotifier(
getBoolUsecase: ref.read(getBoolUsecaseProvider),
setBoolUsecase: ref.read(setBoolUsecaseProvider),
removeCacheUsecase: ref.read(removeCacheUsecaseProvider),
),
);
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 · 157 lines · 0 tokens per session scan A fd977ad79b92
feature-settings 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 1,335 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
cursorrules
Kortix is a React Native + Expo app built with TypeScript, NativeWind (Tailwind CSS), and a custom design system.
nativescript
NativeScript best practices and patterns for mobile applications.
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.
project-structure
Cursor rule "project-structure" from HeeGyeong/ComposeSample, covering project structure guide, layer structure, modularization rules, dependency rules and resource management.
ios-ui-development-focus
UI/UX and SwiftUI best practices - HIG compliance, presentation APIs, layout patterns.