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 instructions/fluttersdk/wind/testsgit clone --depth 1 https://github.com/fluttersdk/windWhat 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.01099 | $0.01099 |
| Opus 5 | $0.00549 | $0.00549 |
| Sonnet 5 | $0.00220 | $0.00220 |
| Haiku 4.5 | $0.00110 | $0.00110 |
Grade A, and why
wind tests.instructions.md 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 yesterday.
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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test conventions (test/)
Layout mirror
test/ mirrors lib/src/ exactly. One production file → one test file:
lib/src/widgets/w_button.dart→test/widgets/w_button_test.dartlib/src/parser/parsers/padding_parser.dart→test/parser/parsers/padding_parser_test.dart
For widgets with large surface area, sub-directory: test/widgets/w_div/spacing_test.dart, test/widgets/w_div/overflow_test.dart, etc. Mirror that under test/widgets/<name>/.
Required setUp
Parser tests + every widget test that pumps className-styled widgets:
setUp(() {
WindParser.clearCache();
});
Skipping WindParser.clearCache() is the single biggest source of false-positive cross-test pollution. The parser cache persists between tests; a sibling test priming the cache makes the next test report PASS even when the production logic regressed.
Canonical helpers (duplicate per file, no shared extraction)
Widget tests define wrapWithTheme at the top:
Widget wrapWithTheme(Widget child) {
return MaterialApp(
home: WindTheme(
data: WindThemeData(),
child: Scaffold(body: child),
),
);
}
Parser tests define createTestContext at the top with 7-8 named params:
WindContext createTestContext({
bool isHovering = false,
bool isFocused = false,
bool isDisabled = false,
String activeBreakpoint = 'md',
Brightness brightness = Brightness.light,
String platform = 'web',
bool isMobile = false,
}) => WindContext(
theme: testTheme,
screenWidth: 400,
screenHeight: 800,
activeBreakpoint: activeBreakpoint,
brightness: brightness,
platform: platform,
isMobile: isMobile,
activeStates: {
if (isHovering) 'hover',
if (isFocused) 'focus',
if (isDisabled) 'disabled',
},
);
Duplicate is intentional — keeps each file's helper trivially editable for local tweaks. Do not extract into test/test_utils.dart.
No mockito
Wind tests use NO mocking library. Fake via:
- Constructor injection (
WActionHandler(actions: {'foo': (args) => ...}, state: WDynamicState())) - Stub widgets that implement the contract
debugDefaultTargetPlatformOverrideforPlatform.is*paths (insidetry/finally— reset is mandatory)
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.
- yesterday First seen · 132 lines · 1,099 tokens per session scan A cf2218da7efd
wind tests.instructions.md is an instructions file published in the GitHub repository fluttersdk/wind (33 stars, last pushed 2d ago), licensed MIT. It adds 1,099 tokens to every session, about $0.0055 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 instructions, from other repositories
mobile CLAUDE.md
Claude Code instructions for lichess-org/mobile, covering claude.md, project overview, development setup, initial setup and install dependencies.
dart_agent_core AGENTS.md
Instructions for memex-lab/dart_agent_core, covering agents.md, common commands, transcript viewer cli (reads eval traces), two public libraries and architecture (big picture).
sanad-agent AGENTS.md
Instructions for EastStarAI/sanad-agent, covering sanad agent repository contract, 1. documentation hierarchy, rules for ai agents and developers, 1.1. the strict separation pact and 1.2. the living project wiki & incremental documentation.
terradart CLAUDE.md
Instructions for nozomi-koborinai/terradart: Use AGENTS.md as the shared project guide. Read CONTEXT.md for project vocabulary before design work.
dart-sdk-skills AGENTS.md
Instructions for RandalSchwartz/dart-sdk-skills, covering ai agent developer handbook (agents.md), 🎯 repository purpose, 🔄 runbook 1: updating for new dart sdk releases, 🔄 runbook 2: updating for new flutter framework releases and 📏 quality & style guidelines.
dart-expert-skills copilot-instructions.md
Instructions for Poorgramer-Zack/dart-expert-skills, covering flutter skills repository - copilot instructions, repository overview, architecture, directory structure and skill structure.