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 kouroshez/coding-os --skill fluttergit clone --depth 1 https://github.com/kouroshez/coding-osWrote 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/kouroshez/coding-os/flutter)<a href="https://agentmods.dev/skills/kouroshez/coding-os/flutter"><img src="https://agentmods.dev/badge/skills/kouroshez/coding-os/flutter/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/kouroshez/coding-os/flutter"><img src="https://agentmods.dev/badge/skills/kouroshez/coding-os/flutter.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.00107 | $0.00849 |
| Opus 5 | $0.00053 | $0.00425 |
| Sonnet 5 | $0.00021 | $0.00170 |
| Haiku 4.5 | $0.00011 | $0.00085 |
Grade A, and why
flutter 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 5d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
REQUIRED BACKGROUND: You MUST also follow clean-code (naming, structure, error paths), frontend-fundamentals (three-state async UI), and a11y (screen-reader semantics). This skill adds Flutter-specific patterns on top.
Anatomy reference: references/anatomy.md. Read that file BEFORE writing any new screen / widget / provider.
flutter
Layer contract (matches structure.tree)
| Layer | May import | Never |
|---|---|---|
screens/ (ConsumerWidget) |
the feature provider, widgets | services, other screens |
state/ (provider / notifier) |
services, other providers | Flutter widgets/material, BuildContext |
services/ |
HTTP client, storage, platform channels | providers, widgets |
widgets/ |
the data + callbacks passed in | services, providers it does not render |
core/ (error mapper, router, theme) |
providers (for routing guards) | services |
State stays widget-free — a notifier never imports BuildContext — so it is
unit-testable and a transport swap (REST → GraphQL → local DB) is a
service-layer-only change.
State & DI
- One feature = one provider file (
health_provider.dart) exposing the service binding plus theAsyncValuethe screen watches. ProviderScopeis mounted once inmain.dart; tests override it per case.- Inject services through a
Provider; neverHealthService()insidebuild()— that bypasses overrides and breaks testing. - Prefer
FutureProvider/AsyncNotifierfor async data — theAsyncValuecarries loading/error/data so the screen cannot forget a state.
Widgets (dumb)
- A screen
watches a provider → rendersvalue.when(loading, error, data)→ emits intents via callbacks. No business logic inbuild(). - Extract reusable presentational pieces into
widgets/; they take data in and call back out, owning no transport. constconstructor wherever the widget allows — it is the cheapest rebuild win.
Navigation
- ONE declarative router in
core/router.dart(go_router). Widgets navigate by name/path through the router; neverNavigator.push(MaterialPageRoute(...))from deep in the tree.
What ships with it
1 file 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.
- 5d ago First seen · 77 lines · 107 tokens per session scan A ae2bc3fd088f
flutter is a skill published in the GitHub repository kouroshez/coding-os (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 107 tokens to every session and 849 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-09-03.
Other skills, from other repositories
graph-mutation-plan
Cookbook for composing an applygraphmutations plan — stable entitykey patterns, the canonical label/edge vocabulary, evidence/invalidation/confidence discipline, and a worked example. Load this when building a non-trivial mutation plan.
potpie-cli
Use when the task is centered on running, explaining, configuring, or troubleshooting the potpie command: doctor, login, pot management, source registration, search, graph workbench reads/writes, and pot scope behavior.
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.
potpie-project-preferences
Use before writing, modifying, reviewing, refactoring, or testing code so repo/project preferences surface: error handling, file structure, frameworks, logging, dependency choices, testing, security, API style, and naming. Also use after code work when a reusable project preference should be recorded.
phone-harness
Control the user's phone — iPhone through the Mac's iPhone Mirroring window, or an Android over adb: open apps, tap, type, swipe, read the screen.
ui-mobile
Mobile UI patterns - React Native, iOS/Android, touch targets.