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/yendangn/flutter-app-builder/flutter-securitynpx skills add yendangn/flutter-app-builder --skill flutter-securitygit clone --depth 1 https://github.com/yendangn/flutter-app-builderWhat 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.00088 | $0.01108 |
| Opus 5 | $0.00044 | $0.00554 |
| Sonnet 5 | $0.00018 | $0.00222 |
| Haiku 4.5 | $0.00009 | $0.00111 |
Grade A, and why
flutter-security 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 2d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flutter Security
Full reference: template.md
Key rules
Never hardcode secrets
// DON'T
const apiKey = 'sk-live-abc123'; // committed to git → leaked
// DO — load from EnvConfig, injected at build time via --dart-define
final apiKey = getIt<AppConfig>().apiKey; // reads from compile-time env
All sensitive data in SecureStorage — never SharedPreferences
// DON'T
prefs.setString('auth_token', token); // plain text, unencrypted
// DO
await getIt<SecureStorage>().write(key: StorageKeys.authToken, value: token);
Certificate pinning — flavor-configurable
// SecurityInterceptor is registered in DI and injected into buildDio
// Pins configured per flavor in EnvConfig (enableSslPinning + sslPins)
getIt.registerLazySingleton<SecurityInterceptor>(
() => SecurityInterceptor(config: getIt<AppConfig>()),
);
// In buildDio — bypasses when enableSslPinning is false or sslPins is empty
security.apply(dio);
Use SecurityInterceptor with SHA-256 pin matching. Pins live in EnvConfig, not in the interceptor. Never disable in prod.
Strip sensitive data from logs
// In LoggingInterceptor — redact before logging
String _redact(String body) => body
.replaceAll(RegExp(r'"password"\s*:\s*"[^"]*"'), '"password":"[REDACTED]"')
.replaceAll(RegExp(r'"token"\s*:\s*"[^"]*"'), '"token":"[REDACTED]"');
Obfuscate every release build
flutter build apk --release --obfuscate --split-debug-info=build/debug-info
flutter build ipa --release --obfuscate --split-debug-info=build/debug-info
Never ship a release build without --obfuscate.
Validate deep links — never trust the URI blindly
// In GoRouter redirect
if (uri.host != 'app.yourdomain.com') return '/';
Screenshot prevention (sensitive screens)
// Android: in MainActivity.kt
window.setFlags(WindowManager.LayoutParams.FLAG_SECURE,
WindowManager.LayoutParams.FLAG_SECURE)
// Flutter side — call via MethodChannel wrapper
getIt<ScreenSecurityService>().enableSecureMode();
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 117 lines · 88 tokens per session scan A aec142d2ee12
flutter-security is a skill published in the GitHub repository yendangn/flutter-app-builder (5 stars, last pushed 2mo ago), licensed MIT. It adds 88 tokens to every session and 1,108 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
edge-to-edge
Use this skill to migrate your Jetpack Compose app to add adaptive edge-to-edge support and troubleshoot common issues. Use this skill to fix UI components (like buttons or lists) that are obscured by or overlapping with the navigation bar or status bar, fix IME insets, and fix system bar legibility.
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.
referral-program
When the user wants to design, launch, or optimize an in-app referral / invite / share-to-earn program — including reward structure, mechanics, fraud prevention, deep link setup, and viral coefficient measurement. Use when the user mentions "referral program", "invite a friend", "refer and earn", "share to earn"…
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".…