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/naming-conventionsnpx skills add sampaio-tech/flutter-core-modules --skill naming-conventionsgit 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/naming-conventions)<a href="https://agentmods.dev/skills/sampaio-tech/flutter-core-modules/naming-conventions"><img src="https://agentmods.dev/badge/skills/sampaio-tech/flutter-core-modules/naming-conventions.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.1 | $0.00070 | $0.02129 |
| Opus 5 | $0.00035 | $0.01064 |
| Sonnet 5 | $0.00014 | $0.00426 |
| Haiku 4.5 | $0.00007 | $0.00213 |
Grade A, and why
naming-conventions 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 — 294 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Naming Conventions — flutter_core_modules
All conventions below are derived directly from the existing codebase. Every new file or symbol must follow these patterns.
1. Files — snake_case with Semantic Suffix
| Suffix | Contents | Examples |
|---|---|---|
*_usecase.dart |
Domain use case class | get_theme_data_usecase.dart, sync_purchases_usecase.dart |
*_state_notifier.dart |
StateNotifier class | theme_state_notifier.dart, haptic_feedback_state_notifier.dart |
*_repository.dart |
Repository abstract or impl | theme_repository.dart (both layers, in separate dirs) |
*_data_source.dart |
DataSource abstract or impl | firebase_storage_remote_data_source.dart |
*_widget.dart |
Widget class | label_row_widget.dart, switch_row_widget.dart |
*_failure.dart |
Failure sealed class | storage_failure.dart |
| (no suffix) | Hooks, utils, config | safe_effect.dart, debounce.dart, revenue_cat.dart |
2. Classes — PascalCase with Semantic Suffix
Use Cases
Pattern: {Verb}{Entity}Usecase
| Verb | Examples |
|---|---|
Get |
GetThemeDataUsecase, GetLocaleUsecase, GetCustomerInfoUsecase, GetDownloadUrlUsecase, GetJsonUsecase, GetAppUserIdUsecase |
Set |
SetThemeDataUsecase, SetLocaleUsecase |
Remove |
RemoveThemeDataUsecase, RemoveLocaleUsecase, RemoveCustomerInfoUpdateListenerUsecase |
Sync |
SyncPurchasesUsecase |
Invalidate |
InvalidateCustomerInfoCacheUsecase |
Add |
AddCustomerInfoUpdateListenerUsecase |
Track |
TrackEventUsecase |
Is |
IsAvailableUsecase |
Request |
RequestReviewUsecase |
Open |
OpenStoreListingUsecase |
State Notifiers
Pattern: {Feature}StateNotifier
ThemeStateNotifier
HapticFeedbackStateNotifier
WakelockStateNotifier
CustomerInfoStateNotifier
GetDownloadUrlStateNotifier
GetJsonStateNotifier
InAppReviewStateNotifier
LaunchFeedbackStateNotifier
Repositories
Pattern: abstract = {Feature}Repository, concrete = {Technology}{Feature}Repository or {Feature}RepositoryImpl
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 · 294 lines · 70 tokens per session scan A 883d016e69b5
naming-conventions is a skill published in the GitHub repository sampaio-tech/flutter-core-modules (2 stars, last pushed 14d ago), licensed MIT. It adds 70 tokens to every session and 2,129 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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…
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…