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 skills add divinevideo/divine-mobile --skill flutter-macos-permission-handler-camera-failuregit clone --depth 1 https://github.com/divinevideo/divine-mobileWrote 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/skills/divinevideo/divine-mobile/flutter-macos-permission-handler-camera-failure)<a href="https://agentmods.dev/skills/divinevideo/divine-mobile/flutter-macos-permission-handler-camera-failure"><img src="https://agentmods.dev/badge/skills/divinevideo/divine-mobile/flutter-macos-permission-handler-camera-failure.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 52 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00125 | $0.01302 |
| Opus 5 | $0.00063 | $0.00651 |
| Sonnet 5 | $0.00025 | $0.00260 |
| Haiku 4.5 | $0.00013 | $0.00130 |
Grade A, and why
flutter-macos-permission-handler-camera-failure 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 8d 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flutter macOS permission_handler Camera Failure
Problem
Camera/microphone permission checks using the permission_handler Flutter plugin throw
exceptions on macOS desktop, causing permission gates to emit error states. The camera
screen never renders, but the user sees a placeholder UI with no clear error message.
Context / Trigger Conditions
Use this skill when:
- Flutter app works on iOS/Android but camera fails on macOS
- Permission gate shows loading or error state on macOS
- Logs show
CameraPermissionErrorstate being emitted Permission.camera.statusorPermission.microphone.statusthrows exceptions- Camera placeholder UI appears but
VideoRecorderScreen(or equivalent) never initializes - No camera-related logs appear after navigation to camera screen
Key diagnostic pattern:
🔐 CameraPermissionGate initState
🔐 Building with state: CameraPermissionInitial
🔐 Triggering permission refresh
🔐 Permission state changed: CameraPermissionError <-- This is the tell
Root Cause
The permission_handler plugin uses platform channels that don't work reliably on macOS
desktop. When checkCameraStatus() or checkMicrophoneStatus() is called:
- On iOS/Android: Returns proper permission status
- On macOS: Throws exception → BLoC catches → Emits error state → Screen blocked
macOS handles camera/microphone permissions at the system level - the first time an app tries to access the camera, macOS shows its own permission dialog.
Solution
Bypass permission_handler on macOS and assume permissions are authorized:
Future<void> _onRefresh(
CameraPermissionRefresh event,
Emitter<CameraPermissionState> emit,
) async {
// On macOS desktop, permission_handler doesn't work reliably.
// macOS handles camera permissions at the system level when the app
// actually tries to access the camera, showing its own permission dialog.
if (!kIsWeb && Platform.isMacOS) {
emit(const CameraPermissionLoaded(CameraPermissionStatus.authorized));
return;
}
// Normal permission check for iOS/Android
try {
final status = await checkPermissions();
emit(CameraPermissionLoaded(status));
} catch (e) {
emit(const CameraPermissionError());
}
}
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.
- 8d ago First seen · 158 lines · 125 tokens per session scan A 01b18109d65b
flutter-macos-permission-handler-camera-failure is a skill published in the GitHub repository divinevideo/divine-mobile (265 stars, last pushed yesterday), licensed MPL-2.0. It adds 125 tokens to every session and 1,302 once invoked, about $0.0006 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-30.
Other skills, from other repositories
ios-fix
Autonomous iOS bug fixer. (gstack).
google-mobile-ads-validate
Validates a project's Google Mobile Ads (GMA) SDK integration for iOS, Android, or Unity projects. Use when conducting a full pre-launch audit of an app that integrates GMA SDK or when validating any individual GMA SDK integration checks, such as when validating ad unit IDs and ad formats, SKAdNetwork IDs, mediation…
competition-ios-runtime
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for IPA runtime analysis, Frida hooks, Objective-C or Swift method tracing, Keychain inspection, SSL pinning bypass, URL scheme handling, and iOS request-signing recovery. Use when the user asks to hook an IPA, trace Objective-C or Swift…
swiftui-performance-audit
SwiftUI performance: render, scroll, CPU/memory, updates, layout, Instruments.
android-tombstone-symbolication
Symbolicate the .NET runtime frames in an Android tombstone file. Extracts BuildIds and PC offsets from the native backtrace, downloads debug symbols from the Microsoft symbol server, and runs llvm-symbolizer to produce function names with source file and line numbers. USE FOR triaging a .NET MAUI or Mono Android app…
node-connect
Diagnose OpenClaw node connection and pairing failures for Android, iOS, and macOS companion apps. Use when QR/setup code/manual connect fails, local Wi-Fi works but VPS/tailnet does not, or errors mention pairing required, unauthorized, bootstrap token invalid or expired, gateway.bind, gateway.remote.url, Tailscale…