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 ariaramin/flutter-skills --skill flutter-dio-engineeringgit clone --depth 1 https://github.com/ariaramin/flutter-skillsWrote 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/ariaramin/flutter-skills/flutter-dio-engineering)<a href="https://agentmods.dev/skills/ariaramin/flutter-skills/flutter-dio-engineering"><img src="https://agentmods.dev/badge/skills/ariaramin/flutter-skills/flutter-dio-engineering/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/ariaramin/flutter-skills/flutter-dio-engineering"><img src="https://agentmods.dev/badge/skills/ariaramin/flutter-skills/flutter-dio-engineering.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00132 | $0.03939 |
| Opus 5.5 | $0.00053 | $0.01576 |
| Sonnet 5.5 | $0.00026 | $0.00788 |
| Haiku 4.5 | $0.00013 | $0.00394 |
Grade A, and why
flutter-dio-engineering 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 6d 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 — 410 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flutter Dio Engineering
Operating stance
Treat Dio as the transport layer, not the application architecture. Preserve this priority order:
- correctness
- security
- reliability
- maintainability
- testability
- performance
- scalability
- developer experience
Apply these invariants:
- Reuse a coherently configured
Dioinstance; do not constructDio()per request. - Interpret reuse by networking-policy boundary, not as one mutable process-global client for unrelated origins or security policies.
- Keep Dio behind typed API/data abstractions; widgets and state-management code should not depend on raw Dio internals.
- Map
DioExceptioninto application/repository failures at the data boundary. - Keep business rules and navigation out of interceptors.
- Keep dynamic credentials out of long-lived static
BaseOptions.headers. - Filter endpoint-specific policy through request
Options/extrainstead of mutating global client state. - Prevent token-refresh recursion and concurrent refresh storms.
- Retry only when method/backend semantics make repetition safe; bound attempts and total cost.
- Treat intentional cancellation separately from connectivity failure.
- Use streaming/file-oriented APIs for large transfers instead of buffering without need.
- Never log bearer tokens, refresh tokens, cookies, passwords, confidential credentials, payment data, or sensitive bodies.
- Never disable TLS verification in production.
- Do not attempt to solve Web CORS with client-side
Access-Control-Allow-*request headers. - Test networking deterministically through injected clients/adapters; ordinary unit tests must not require live production services.
- Profile before replacing current Dio defaults such as its transformer or adapter.
Version and evidence gate
The supplied guide targets current Dio 5.x behavior and specifically discusses Dio 5.11-era APIs such as transformTimeout, FusedTransformer, current multipart behavior, and concurrency fixes.
Before editing a repository:
What ships with it
5 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.
- 6d ago First seen · 410 lines · 132 tokens per session scan A 98970c517849
flutter-dio-engineering is a skill published in the GitHub repository ariaramin/flutter-skills (6 stars, last pushed 7d ago), licensed MIT. It adds 132 tokens to every session and 3,939 once invoked, about $0.0005 per session on Opus 5.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-10-11.
Other skills, from other repositories
event-driven-design
When designing loosely coupled systems that react to state changes asynchronously.
error-handling-architecture
When designing how a system recovers from and reports failures.
api-design-rest
When creating or extending an HTTP API for client consumption.
open-source
Documentation reference for writing Python code using the browser-use open-source library. Use this skill whenever the user needs help with Agent, Browser, or Tools configuration, is writing code that imports from browseruse, asks about @sandbox deployment, supported LLM models, Actor API, custom tools, lifecycle…
potpie-infra-architecture
Use for project infra and architecture context: environments, adapters, runtime configuration, deployments, service dependencies, datastores, API contracts, ownership, incidents, and dependency blast radius.
build-teaql-app
Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C#/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries. Mandatory order: first draft and save a complete KSML model, then verify the client and evaluate that saved model, repair it through repeated evaluation…