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 agentmods add skills/sampaio-tech/flutter-core-modules/core-architecturenpx skills add sampaio-tech/flutter-core-modules --skill core-architecturegit clone --depth 1 https://github.com/sampaio-tech/flutter-core-modulesWrote 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/sampaio-tech/flutter-core-modules/core-architecture)<a href="https://agentmods.dev/skills/sampaio-tech/flutter-core-modules/core-architecture"><img src="https://agentmods.dev/badge/skills/sampaio-tech/flutter-core-modules/core-architecture.svg" alt="Measured on agentmods" 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 | $0.00068 | $0.03373 |
| Opus 5 | $0.00034 | $0.01687 |
| Sonnet 5 | $0.00014 | $0.00675 |
| Haiku 4.5 | $0.00007 | $0.00337 |
Grade A, and why
core-architecture 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 — 400 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Core Architecture — flutter_core_modules
This package is a shared Flutter library providing clean-architecture foundations consumed by multiple apps. It lives at lib/src/core/ and everything here is re-exported via lib/flutter_core_modules.dart.
1. Either — Functional Error Handling
File: lib/src/core/domain/utils/either.dart
A custom sealed class Either<L, R> (no external dependency) inspired by Scala/dartz:
sealed class Either<L, R> {
T fold<T>(T Function(L) fa, T Function(R) fb);
}
class Right<L, R> extends Either<L, R> { R get value; }
class Left<L, R> extends Either<L, R> { L get value; }
Convention: L is always the Failure type, R is the success value.
All use cases and repositories that can fail return Future<Either<Failure, Entity>>. Never throw exceptions across layer boundaries — wrap them in Left.
// Correct pattern in a use case:
Future<Either<StorageFailure, String>> call(...) =>
_repository.getDownloadUrl(...);
// Consuming in a notifier:
final failureOrSuccess = await forwardedGet();
state = failureOrSuccess.fold(
LoadFailureState.new,
LoadSuccessState.new,
);
2. State — Sealed State Machine
File: lib/src/core/presentation/notifiers/state.dart
sealed class State<F, S> {}
class StartedState<F, S> extends State<F, S> {} // initial, no data
class LoadInProgressState<F, S> extends State<F, S> {} // loading, optional prev data
class LoadSuccessState<F, S> extends State<F, S> { S get value; }
class LoadFailureState<F, S> extends State<F, S> { F get value; }
F= Failure type (e.g.,StorageFailure)S= Success type (e.g.,String,CustomerInfo)LoadInProgressStateoptionally carries previousf/sfor "loading with previous data" UX patterns.
Pattern-matching in UI:
switch (state) {
StartedState() => const SizedBox.shrink(),
LoadInProgressState() => const CircularProgressIndicator(),
LoadSuccessState(value: final url) => Image.network(url),
LoadFailureState() => ErrorIndicatorWidget(...),
}
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 · 400 lines · 68 tokens per session scan A e1c3386dac0c
core-architecture is a skill published in the GitHub repository sampaio-tech/flutter-core-modules (2 stars, last pushed 13d ago), licensed MIT. It adds 68 tokens to every session and 3,373 once invoked, about $0.0003 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
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…