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.
npx agentmods add rules/sampaio-tech/flutter-core-modules/feature-routegit clone --depth 1 https://github.com/sampaio-tech/flutter-core-modulesWhat 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 | $0.00000 | $0.01122 |
| Opus 5 | $0.00000 | $0.00561 |
| Sonnet 5 | $0.00000 | $0.00224 |
| Haiku 4.5 | $0.00000 | $0.00112 |
Grade A, and why
feature-route 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 yesterday.
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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature: Route — Rules
What Is Already Implemented — Check Before Building
| Capability | Status |
|---|---|
iOS tab scaffold (CupertinoTabScaffold) |
✅ ShellRouteWidget |
| Pop-to-root on active tab double-tap | ✅ Built into ShellRouteWidget |
| System back handling | ✅ PopScope in ShellRouteWidget |
| Per-tab isolated navigator | ✅ CupertinoTabView per tab |
Stable GlobalKey<NavigatorState> per tab |
✅ navigatiorKeyProvider (family provider) |
| Analytics screen tracking (Firebase + PostHog) | ✅ defaultNavigatorObservers() |
Deep-link / go_router integration |
❌ Not in package — implement in consuming app |
| Bottom tab badge / notification dot | ❌ Not in package — extend NavigationTab |
Custom tab bar beyond activeColor |
❌ Uses CupertinoTabBar — only activeColor is configurable |
Before building navigation infrastructure, verify whether ShellRouteWidget already covers the requirement.
Layer Structure
lib/src/features/route/
└── presentation/
├── utils/navigation_observers.dart # defaultNavigatorObservers()
└── widgets/shell_route_widget.dart # ShellRouteWidget, NavigationTab, navigatiorKeyProvider
This feature is presentation-only — no domain or data layers.
Implementing a Tab
class HomeTab extends NavigationTab {
const HomeTab() : super(
name: 'home', // unique string identifier
icon: CupertinoIcons.house_fill,
initialTab: true, // only one tab should have initialTab: true
);
@override
String label(BuildContext context) => AppLocalizations.of(context)!.home;
@override
Map<String, Widget Function(BuildContext)>? get routes => {
'/': (context) => const HomeScreen(),
'/detail': (context) => const DetailScreen(),
};
@override
List<NavigatorObserver> navigatorObservers(BuildContext context) =>
defaultNavigatorObservers(context); // always include for analytics
}
Rules for NavigationTab subclasses:
namemust be unique across all tabs in the app- Only one tab per
ShellRouteWidgetshould haveinitialTab: true - Always override
navigatorObserversto returndefaultNavigatorObservers(context)unless you have a specific reason not to track screen views
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.
- yesterday First seen · 131 lines · 0 tokens per session scan A e2b8cbe5c71d
feature-route is a cursor rule published in the GitHub repository sampaio-tech/flutter-core-modules (2 stars, last pushed 10d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,122 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.
git-commit-attribution
Git commits must use the human developer identity only; never Cursor Agent co-authorship.
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.
cursorrules
ROLE: Android Development Expert EXPERIENCELEVEL: Advanced (10+ years) SPECIALTIES.
ios-ui-development-focus
UI/UX and SwiftUI best practices - HIG compliance, presentation APIs, layout patterns.