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/strvcom/flutter-template/widget-testnpx skills add strvcom/flutter-template --skill widget-testgit clone --depth 1 https://github.com/strvcom/flutter-templateWhat 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.00065 | $0.00926 |
| Opus 5 | $0.00032 | $0.00463 |
| Sonnet 5 | $0.00013 | $0.00185 |
| Haiku 4.5 | $0.00006 | $0.00093 |
Grade A, and why
widget-test 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flutter Template Widget Tests
Use this skill when adding focused widget coverage for a screen, shared component, or UI state in this Flutter template.
Read First
AGENTS.mddocs/PROJECT_OVERVIEW.mddocs/PROJECT_GUIDELINES.md- Nearby tests under
test/ - The widget, provider, and state files being covered
When To Add Widget Tests
- A shared widget gets new behavior, styling states, callbacks, or accessibility expectations.
- A feature screen adds meaningful loading, empty, error, or success states.
- A bug fix changes what the user sees or can tap.
- A regression would be cheap to catch with a
pumpWidgettest.
Do not add broad snapshot-style tests that only restate the widget tree. Prefer behavior and contract checks: visible text, enabled/disabled states, callbacks, navigation events, empty/error rendering, and provider-driven state transitions.
Test Location
- Shared UI:
test/common/<widget_name>_test.dart - Feature UI:
test/features/<feature>/<feature>_page_content_test.dart - Provider-heavy feature states may also need focused provider tests; keep them near the feature test folder unless the repo already has a stronger local pattern.
Harness Pattern
Call Configuration.setup(flavor: Flavor.develop) at the top of main() before any test runs —
existing tests in test/common/ do this and widgets that read configuration fail without it.
Build the smallest wrapper that gives the widget the dependencies it expects:
Widget buildSubject({
List<Override> overrides = const [],
}) {
return ProviderScope(
overrides: overrides,
child: MaterialApp(
localizationsDelegates: AppLocalizations.localizationsDelegates,
supportedLocales: AppLocalizations.supportedLocales,
theme: AppTheme.getThemeData(brightness: Brightness.light),
home: const Scaffold(
body: SubjectWidget(),
),
),
);
}
Adapt imports to the current code. If the existing nearby tests use patrolWidgetTest,
pumpWidgetAndSettle, or another helper, reuse that style instead of creating a parallel harness.
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 · 103 lines · 65 tokens per session scan A 52a18e83d972
widget-test is a skill published in the GitHub repository strvcom/flutter-template (24 stars, last pushed 2mo ago), licensed MIT. It adds 65 tokens to every session and 926 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-30.
Other skills, from other repositories
planning-with-files-ar
تخطيط مستمر قائم على الملفات لعمل وكلاء الذكاء الاصطناعي متعدد الخطوات. يحتفظ بملفات taskplan.md و findings.md و progress.md على القرص، وتحقن خطافات دورة الحياة سياق التخطيط المحدد للمشروع. تقرأ الاستعادة التلقائية ملفات تخطيط المشروع فقط. يمكن للأمر الصريح session-catchup.py --metadata فحص بيانات وصفية لجلسات الوكيل…
kl-consistency-test
Write, calibrate, and debug the prefill-vs-decode logprob (KL) consistency tests in sglang -- the two independent conditions a zero requires (every operator batch-invariant, and the two paths computing the same function), which helper separates them, how to pick a threshold once they hold, and how to localize a…
i18n-localization
Internationalization and localization patterns. Detecting hardcoded strings, managing translations, locale files, RTL support.
dsh-web-documentation
Use when adding or editing dsh-web README files, docs, AGENTS.md instructions, user-facing configuration text, or bilingual documentation pairs.
baoyu-youtube-transcript
Downloads YouTube video transcripts/subtitles and cover images by URL or video ID. Supports multiple languages, translation, chapters, and speaker identification. Caches raw data for fast re-formatting. Use when user asks to "get YouTube transcript", "download subtitles", "get captions", "YouTube字幕", "YouTube封面"…
indication-dossier
Build a source-backed biomedical indication dossier. Use when a research task asks for disease biology, target rationale, patient segmentation, biomarkers, trials, drugs, competitive landscape, or translational evidence.