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 skills/sampaio-tech/flutter-core-modules/feature-themenpx skills add sampaio-tech/flutter-core-modules --skill feature-themegit 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.00078 | $0.01789 |
| Opus 5 | $0.00039 | $0.00894 |
| Sonnet 5 | $0.00016 | $0.00358 |
| Haiku 4.5 | $0.00008 | $0.00179 |
Grade A, and why
feature-theme 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 3d 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 — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature: Theme
Purpose: Persist and restore the user's chosen IosThemeData (light or dark) across sessions using SharedPreferences, and expose a reactive ThemeStateNotifier that the app root widget watches to re-theme the entire app.
Layer Map
lib/src/features/theme/
├── domain/
│ ├── repositories/theme_repository.dart # abstract ThemeRepository
│ └── usecases/
│ ├── get_theme_data_usecase.dart # GetThemeDataUsecase + provider
│ ├── set_theme_data_usecase.dart # SetThemeDataUsecase + provider
│ └── remove_theme_data_usecase.dart # RemoveThemeDataUsecase + provider
├── data/
│ └── repositories/theme_repository.dart # ThemeRepositoryImpl + provider
└── presentation/
└── notifiers/
└── theme_state_notifier.dart # ThemeStateNotifier + provider
Domain
Repository Interface
abstract class ThemeRepository {
IosThemeData? getThemeData(); // sync, nullable
Future<bool> setThemeData({required IosThemeData iosThemeData});
Future<bool> removeThemeData();
}
Use Cases
| Class | Provider | Signature |
|---|---|---|
GetThemeDataUsecase |
getThemeDataUsecaseProvider |
IosThemeData? call() |
SetThemeDataUsecase |
setThemeDataUsecaseProvider |
Future<bool> call({required IosThemeData iosThemeData}) |
RemoveThemeDataUsecase |
removeThemeDataUsecaseProvider |
Future<bool> call() |
All providers are Provider.autoDispose.
Data
ThemeRepositoryImpl
File: lib/src/features/theme/data/repositories/theme_repository.dart
Stores the theme as a String (runtime type name) in SharedPreferences:
IosLightThemeData → stored as 'IosLightThemeData'
IosDarkThemeData → stored as 'IosDarkThemeData'
Key: DatabaseKeys.iosThemeData.key → 'iosThemeData' (prod) / 'iosThemeDataDebug' (debug)
// Read: pattern-matches on the stored string to reconstruct the correct subclass
IosThemeData? getThemeData() => switch (_sharedPreferences.getString(key)) {
null => null,
final v when v == IosLightThemeData().runtimeType.toString() => IosLightThemeData(),
final v when v == IosDarkThemeData().runtimeType.toString() => IosDarkThemeData(),
_ => null,
};
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.
- 3d ago First seen · 240 lines · 78 tokens per session scan A f8941bf9cb3c
feature-theme is a skill published in the GitHub repository sampaio-tech/flutter-core-modules (2 stars, last pushed 11d ago), licensed MIT. It adds 78 tokens to every session and 1,789 once invoked, about $0.0004 per session on Opus 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 skills, from other repositories
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
flutter-fix-layout-issues
Fixes Flutter layout errors (overflows, unbounded constraints) using Dart and Flutter MCP tools. Use when addressing "RenderFlex overflowed", "Vertical viewport was given unbounded height", or similar layout issues.
android-pentest
安卓应用渗透测试 — APK分析、Hook、自动化测试、运行态驱动、签名恢复、抓包分析.
ios-hig-design
Design native iOS interfaces following Apple Human Interface Guidelines. Use when the user mentions "iPhone app", "iPad layout", "SwiftUI", "UIKit", "Dynamic Island", "safe areas", "HIG compliance", "SF Symbols", "haptic feedback", "iOS accessibility", "make my app feel native", or "follow Apple design guidelines".…
firebase-remote-config
Use when implementing feature flags, running A/B tests, setting parameter defaults, fetching/activating config, or enabling real-time config updates.
odevio
Take a Flutter project to an iPhone or the App Store with Odevio - build, sign and publish iOS apps from Windows, Linux or macOS with no Mac and no Xcode. Handles Apple setup, certificates, provisioning profiles, code signing, the .ipa, TestFlight and App Store submission, and fixes build failures automatically. Use…