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 Poorgramer-Zack/dart-expert-skills --skill flutter-responsivegit clone --depth 1 https://github.com/Poorgramer-Zack/dart-expert-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/poorgramer-zack/dart-expert-skills/flutter-responsive)<a href="https://agentmods.dev/skills/poorgramer-zack/dart-expert-skills/flutter-responsive"><img src="https://agentmods.dev/badge/skills/poorgramer-zack/dart-expert-skills/flutter-responsive/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/poorgramer-zack/dart-expert-skills/flutter-responsive"><img src="https://agentmods.dev/badge/skills/poorgramer-zack/dart-expert-skills/flutter-responsive.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.00160 | $0.01594 |
| Opus 5 | $0.00080 | $0.00797 |
| Sonnet 5 | $0.00032 | $0.00319 |
| Haiku 4.5 | $0.00016 | $0.00159 |
Grade A, and why
implementing-responsive-layouts 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 10d 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flutter Responsive Implementations (v5.9.x / v3.1.x / v1.1.x)
Goal
Implement layout adaptability and responsive UI across varying device screens. This skill provides a decision matrix to choose the right responsiveness package and strict instructions on how to use flutter_screenutil, sizer, and responsive_framework natively.
Instructions
1. Package Decision Matrix
Before writing layout code, strictly evaluate the project's target platforms and design requirements to select the appropriate library:
- Scenario A (Strict Mobile UI Replication): The project targets only iOS/Android, and the designers have provided a strict Figma draft (e.g., 375x812) that must look exactly proportional on all phones (mini to pro max).
- Decision: Use
flutter_screenutil. (Math-based density scaling)
- Decision: Use
- Scenario B (Percentage-based Mobile UI): The project targets mobile, but layout is dictated by percentage of screen real estate rather than fixed Figma pixels.
- Decision: Use
sizer. (Percentage-based viewport scaling)
- Decision: Use
- Scenario C (True Cross-Platform / Web / Desktop): The project spans Mobile, Tablet, Web, and Desktop. UI components must fundamentally change their structure (e.g. BottomNav -> SideRail) based on available space, rather than just zooming in.
- Decision: Use
responsive_framework. (Breakpoint-based rendering)
- Decision: Use
2. Implementing flutter_screenutil
Best for mathematically scaling a fixed design draft across different physical device sizes.
Setup (main.dart):
Wrap the MaterialApp in ScreenUtilInit and provide the designSize from the design specs (Figma/AdobeXD).
Widget build(BuildContext context) {
return ScreenUtilInit(
designSize: const Size(375, 812), // The Figma draft size
minTextAdapt: true,
splitScreenMode: true,
builder: (context, child) {
return MaterialApp(
// ...
);
},
);
}
Usage Constraints:
- Width: Use
.w(e.g.,100.w) - Height: Use
.h(e.g.,200.h) - Square dimensions / Radius: Use
.r(e.g.,Radius.circular(16.r)) or100.wfor both width and height to prevent stretching. Do not use.hfor width. - Fonts: Use
.sp(e.g.,16.sp). Note:spchanges with system accessibility font sizes.
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.
- 10d ago First seen · 150 lines · 160 tokens per session scan A 55935030c4f9
implementing-responsive-layouts is a skill published in the GitHub repository Poorgramer-Zack/dart-expert-skills (7 stars, last pushed 1mo ago), licensed MIT. It adds 160 tokens to every session and 1,594 once invoked, about $0.0008 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…
signals-hooks
Comprehensive reactive state hooks for integration with flutterhooks.
signals-flutter
Highly optimized Flutter UI bindings and GPU rendering for reactive signals.
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.