Borrowing it
Nothing to install: this file belongs to divinevideo/divine-mobile. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/divinevideo/divine-mobile/main/.agents/skills/flutter-startup-network-blocking/SKILL.mdgit 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-startup-network-blocking)<a href="https://agentmods.dev/skills/divinevideo/divine-mobile/flutter-startup-network-blocking"><img src="https://agentmods.dev/badge/skills/divinevideo/divine-mobile/flutter-startup-network-blocking.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 Data Exfiltration · line 125 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00104 | $0.01056 |
| Opus 5 | $0.00052 | $0.00528 |
| Sonnet 5 | $0.00021 | $0.00211 |
| Haiku 4.5 | $0.00010 | $0.00106 |
Grade A, and why
flutter-startup-network-blocking 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 7d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flutter Startup Network Blocking
Problem
Flutter app startup is slow because network operations (WebSocket connections, API calls, service initialization) run sequentially during the initialization phase, blocking the first frame from rendering. With multiple relay/server connections, worst-case startup time becomes O(n × timeout) instead of O(max timeout).
Context / Trigger Conditions
- App takes 3+ seconds to show first frame on fresh launch
- Startup logs show sequential "connecting to relay X... connecting to relay Y..."
- Services that require authentication initialize even for unauthenticated users
_initializeCoreServices()or similar contains multiple awaited network operations- Riverpod providers eagerly initialize network-dependent services in their
build()method
Solution
1. Identify Blocking Operations
Look for sequential awaits in startup code:
// BAD: Sequential - each connection blocks the next
for (final url in relays) {
await connectToRelay(url); // Blocks startup!
}
2. Convert Sequential to Parallel
Use Future.wait() to run all connections simultaneously:
// GOOD: Parallel - all connections run at once
final results = await Future.wait(
relays.map((url) async {
final success = await connectToRelay(url);
return MapEntry(url, success);
}),
);
3. Defer Non-Critical Service Initialization
Move network-dependent services out of the critical startup path:
Before (blocking startup):
Future<void> _initializeCoreServices(ProviderContainer container) async {
await container.read(authServiceProvider).initialize();
await container.read(nostrServiceProvider).initialize(); // BLOCKS for relay connections!
await container.read(otherServiceProvider).initialize();
}
After (lazy initialization):
Future<void> _initializeCoreServices(ProviderContainer container) async {
// NOTE: NostrService initializes lazily when user authenticates
await container.read(authServiceProvider).initialize();
await container.read(seenVideosServiceProvider).initialize();
// NostrService NOT initialized here - happens when auth state changes
}
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.
- 7d ago First seen · 127 lines · 104 tokens per session scan A 537589877ee4
flutter-startup-network-blocking is a skill published in the GitHub repository divinevideo/divine-mobile (265 stars, last pushed today), licensed MPL-2.0. It adds 104 tokens to every session and 1,056 once invoked, about $0.0005 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…