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 aleksandr-chaika/flutter-clean-arch-skills --skill flutter-guidegit clone --depth 1 https://github.com/aleksandr-chaika/flutter-clean-arch-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/aleksandr-chaika/flutter-clean-arch-skills/flutter-guide)<a href="https://agentmods.dev/skills/aleksandr-chaika/flutter-clean-arch-skills/flutter-guide"><img src="https://agentmods.dev/badge/skills/aleksandr-chaika/flutter-clean-arch-skills/flutter-guide/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/aleksandr-chaika/flutter-clean-arch-skills/flutter-guide"><img src="https://agentmods.dev/badge/skills/aleksandr-chaika/flutter-clean-arch-skills/flutter-guide.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.00039 | $0.01574 |
| Opus 5 | $0.00019 | $0.00787 |
| Sonnet 5 | $0.00008 | $0.00315 |
| Haiku 4.5 | $0.00004 | $0.00157 |
Grade A, and why
flutter-guide 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 — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flutter Guide — Clean Architecture + BLoC
Reference Guide
| Topic | Reference | Use When |
|---|---|---|
| Clean Architecture | references/clean-architecture.md |
Layer rules, dependency direction |
| BLoC Patterns | references/bloc-patterns.md |
@freezed events/states, handlers, transformers |
| UI Guidelines | references/ui-guidelines.md |
AppColors, AppTextStyles, SVGImage |
| Review Checklist | references/review-checklist.md |
Code review, quality checks |
| Mocking Guide | references/mocking-guide.md |
Mocktail, MockBloc, ProviderContainer |
| Test Patterns | references/test-patterns.md |
UseCase tests, BLoC tests, widget tests |
Project Structure
lib/
├── core/ # AppError, extensions, DI (GetIt)
├── data/
│ ├── mapper/ # Entity <-> Model mappers
│ ├── network/ # API client, models (@JsonSerializable), interceptors
│ ├── repository/ # Repository implementations
│ └── services/
├── domain/
│ ├── entity/ # Domain entities (@freezed)
│ ├── repository/ # Abstract interfaces
│ ├── services/
│ └── usecases/
├── presentation/
│ ├── {feature}/
│ │ ├── bloc.dart # FeatureBloc
│ │ ├── events.dart # @freezed events
│ │ ├── states.dart # @freezed states
│ │ └── view/ # Pages + widgets
│ └── common/
└── resources/ # Colors, text styles, localization
Dependency Rule
Presentation -> Domain <- Data — Domain depends on NOTHING.
Critical Rules
1. MANDATORY: @freezed for Events and States
@freezed
class FeatureEvent with _$FeatureEvent {
const factory FeatureEvent.started() = _Started;
const factory FeatureEvent.loadData({required int id}) = _LoadData;
}
@freezed
class FeatureState with _$FeatureState {
const factory FeatureState.initial() = _Initial;
const factory FeatureState.loading() = _Loading;
const factory FeatureState.loaded(Data data) = _Loaded;
const factory FeatureState.error(AppError error) = _Error;
}
What ships with it
6 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.
- 10d ago First seen · 211 lines · 39 tokens per session scan A b0eb822596a5
flutter-guide is a skill published in the GitHub repository aleksandr-chaika/flutter-clean-arch-skills (5 stars, last pushed 6mo ago), licensed MIT. It adds 39 tokens to every session and 1,574 once invoked, about $0.0002 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
android-kotlin-compose
Android development with Kotlin and Jetpack Compose. Use when user mentions "Compose", "Jetpack Compose", "Material3", "Hilt", "Room", "ViewModel", or needs to build Android UI, implement MVVM architecture, manage Compose state, or integrate Jetpack libraries (Navigation, Room, Hilt, ViewModel). Triggers on…
android-kotlin-coroutines
Android development with Kotlin Coroutines and Flow. Use when user mentions "coroutines", "suspend", "Flow", "StateFlow", "SharedFlow", "viewModelScope", "lifecycleScope", or needs to implement async programming, handle structured concurrency, integrate coroutines with Retrofit/Room/WorkManager, or write coroutine…
testing-go
Writes tests following TDD (using go test, testify, and rapid) best practices. Use when writing unit tests, integration tests, or table-driven tests in Go.
testing-python
Writes tests following TDD Red-Green-Refactor (pytest + Hypothesis). Tests behavior, not implementation. Use when writing unit tests, integration tests, or property tests.
testing-rust
Writes tests following TDD (using cargo test, proptest, and insta) best practices. Use when writing unit tests, integration tests, or property-based tests in Rust.
testing-tdd
Writes tests following TDD Red-Green-Refactor cycle. Language-agnostic methodology with Arrange-Act-Assert structure. Use when implementing features test-first.