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/yendangn/flutter-app-builder/flutter-loggingnpx skills add yendangn/flutter-app-builder --skill flutter-logginggit clone --depth 1 https://github.com/yendangn/flutter-app-builderWhat 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.00054 | $0.00666 |
| Opus 5 | $0.00027 | $0.00333 |
| Sonnet 5 | $0.00011 | $0.00133 |
| Haiku 4.5 | $0.00005 | $0.00067 |
Grade A, and why
flutter-logging 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 2d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flutter Logging
Full reference: template.md
Key rules
AppLoggeris the app-owned interface. Never importpackage:logger/logger.dartoutsidelogger_impl.dart.- Four log levels:
debug,info,warn,error. All accept optionalerrorandstackTraceparams. LoggerImplwraps theloggerpackage. Configured withPrettyPrinterin dev/uat,SimplePrinterin prod.- Logging is enabled based on
AppConfig.enableLogging. Prod builds log only errors. - Wire
AppLoggerintoBlocObserverto log state transitions and errors automatically. - Route observer (
RouteObserver) logs page pushes/pops for screen tracking. - Pass
AppLoggervia constructor injection — never resolve viagetItinside business logic.
AppBlocObserver pattern
Set in bootstrap — logs every cubit state change and routes all bloc errors to ErrorHandler:
class AppBlocObserver extends BlocObserver {
AppBlocObserver({required AppLogger logger, required ErrorHandler errorHandler})
: _logger = logger, _errorHandler = errorHandler;
final AppLogger _logger;
final ErrorHandler _errorHandler;
@override
void onError(BlocBase<dynamic> bloc, Object error, StackTrace stackTrace) {
super.onError(bloc, error, stackTrace);
_errorHandler.handleError(error, stackTrace, reason: '${bloc.runtimeType} error');
}
@override
void onChange(BlocBase<dynamic> bloc, Change<dynamic> change) {
super.onChange(bloc, change);
_logger.debug('${bloc.runtimeType}: state → ${change.nextState.runtimeType}');
}
}
Bootstrap wiring:
Bloc.observer = AppBlocObserver(
logger: getIt<AppLogger>(),
errorHandler: getIt<ErrorHandler>(),
);
Route observer
AppRouteObserver extends NavigatorObserver — logs screen pushes/pops. Wire into GoRouter observers:
final router = GoRouter(
observers: [AppRouteObserver(logger: getIt<AppLogger>())],
);
Files
lib/src/core/logging/
app_logger.dart ← interface (debug / info / warn / error)
logger_impl.dart ← only file that imports package:logger
lib/src/core/bloc/
app_bloc_observer.dart ← logs BLoC state changes + routes errors to ErrorHandler
app_route_observer.dart ← logs screen push/pop via NavigatorObserver
What ships with it
4 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.
- 2d ago First seen · 80 lines · 54 tokens per session scan A e47569bf75a9
flutter-logging is a skill published in the GitHub repository yendangn/flutter-app-builder (5 stars, last pushed 2mo ago), licensed MIT. It adds 54 tokens to every session and 666 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…