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/nylo-core/claude-code/flutter-permissionsnpx skills add nylo-core/claude-code --skill flutter-permissionsgit clone --depth 1 https://github.com/nylo-core/claude-codeWhat 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.00051 | $0.03674 |
| Opus 5 | $0.00026 | $0.01837 |
| Sonnet 5 | $0.00010 | $0.00735 |
| Haiku 4.5 | $0.00005 | $0.00367 |
Grade A, and why
flutter-permissions 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 — 416 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flutter Permissions
Overview
Flutter apps must declare permissions in platform-specific configuration files and request them at runtime. iOS uses Info.plist usage description strings, Android uses AndroidManifest.xml permission declarations. Both platforms require runtime permission requests for sensitive capabilities.
When to Use
- User needs to access camera, photos, location, microphone, contacts, or other device features
- App crashes with permission-related errors
- User is adding a plugin that requires platform permissions (e.g., image_picker, geolocator)
- Store review rejected the app for missing usage descriptions (iOS) or excessive permissions
- User wants to implement runtime permission handling
- NOT for internet permission alone on Android (included by default in Flutter)
Quick Reference: Common Permissions
| Feature | iOS Info.plist Key | Android Manifest Permission |
|---|---|---|
| Camera | NSCameraUsageDescription |
android.permission.CAMERA |
| Photo Library (read) | NSPhotoLibraryUsageDescription |
android.permission.READ_MEDIA_IMAGES (API 33+) / READ_EXTERNAL_STORAGE (older) |
| Photo Library (write) | NSPhotoLibraryAddUsageDescription |
android.permission.WRITE_EXTERNAL_STORAGE (API < 29) |
| Microphone | NSMicrophoneUsageDescription |
android.permission.RECORD_AUDIO |
| Location (when in use) | NSLocationWhenInUseUsageDescription |
android.permission.ACCESS_FINE_LOCATION |
| Location (always) | NSLocationAlwaysAndWhenInUseUsageDescription |
android.permission.ACCESS_BACKGROUND_LOCATION |
| Contacts | NSContactsUsageDescription |
android.permission.READ_CONTACTS |
| Calendar | NSCalendarsUsageDescription |
android.permission.READ_CALENDAR |
| Reminders | NSRemindersUsageDescription |
(use Calendar permission) |
| Bluetooth | NSBluetoothAlwaysUsageDescription |
android.permission.BLUETOOTH_CONNECT (API 31+) / BLUETOOTH (older) |
| Notifications | Not in Info.plist (requested via API) | android.permission.POST_NOTIFICATIONS (API 33+) |
| Face ID | NSFaceIDUsageDescription |
N/A |
| Speech Recognition | NSSpeechRecognitionUsageDescription |
android.permission.RECORD_AUDIO |
| Motion & Fitness | NSMotionUsageDescription |
android.permission.ACTIVITY_RECOGNITION (API 29+) |
| Local Network | NSLocalNetworkUsageDescription |
N/A |
| Tracking (ATT) | NSUserTrackingUsageDescription |
com.google.android.gms.permission.AD_ID |
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 · 416 lines · 51 tokens per session scan A 19335504dd86
flutter-permissions is a skill published in the GitHub repository nylo-core/claude-code (4 stars, last pushed 4mo ago), licensed MIT. It adds 51 tokens to every session and 3,674 once invoked, about $0.0003 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
at_client_skills-sdk
Use this skill when a developer is building a Dart or Flutter app that depends on atclient or atclientflutter from pub.dev, stores or shares data via the Atsign Protocol, needs onboarding (CRAM new-atsign, atKeys file, keychain, APKAM) or APKAM enrollment, or asks about AtCollection , CItem , Query , sub-collections…
flutter-pre-caching
Use when preloading fonts, asset/network images, Lottie/Rive animations, local JSON/config, warming initial API data, or optimizing Flutter Web startup.
firebase-messaging
Use when setting up Firebase Cloud Messaging, managing permissions and tokens, handling background/foreground notification taps, or dispatching messages server-side (HTTP v1).
bloc
Use when creating a Cubit or Bloc, modeling state with sealed classes or status enums, wiring BlocBuilder/BlocListener/BlocProvider, writing bloc tests, or choosing between Cubit and Bloc.
firebase-auth
Use when setting up auth, managing auth state, implementing email/password or social sign-in, handling auth errors, or managing users.
dart-3-updates
Use when writing switch statements, refactoring if-else chains, creating data classes, choosing records vs classes, destructuring values, or modernizing pre-Dart-3 code.