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 rules/consiliency/flutter-structurizr/parser-and-test-consistencygit clone --depth 1 https://github.com/Consiliency/Flutter-StructurizrWhat 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.00000 | $0.00527 |
| Opus 5 | $0.00000 | $0.00264 |
| Sonnet 5 | $0.00000 | $0.00105 |
| Haiku 4.5 | $0.00000 | $0.00053 |
Grade A, and why
parser-and-test-consistency 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Parser and Test Consistency Rules
These rules ensure robust, maintainable, and consistent parser code and tests for Structurizr DSL parsing.
1. Use the Properties Map for Extensible Attributes
- All extensible or user-defined attributes (e.g.,
description,tags, custom properties) must be set and accessed via thepropertiesmap on model nodes. - Do not attempt to set or mutate
finalfields likedescriptionortagsdirectly after construction. - See model_element_node.dart
2. Test Assertions Should Use the Properties Map
- In tests, always check for attribute values using
node.properties?['key']rather than direct field access, unless the field is explicitly non-extensible and public. - See element_parser_test.dart
3. Context Stack Setup for Block/Property Parsing
- Before calling
parseParentChildor similar methods that set properties, push a context with the relevant node ascurrentElementonto theContextStack. - Always pop the context after the test to avoid stack contamination.
- See context_stack.dart
4. ErrorReporter Initialization in Tests
- When constructing an
ErrorReporterin tests, use a non-empty string (e.g.,' ' * 1000) to avoid out-of-bounds errors when reporting errors at specific offsets. - See error_reporter.dart
5. No Monkey-Patching or Method Overrides in Dart Tests
- Dart does not allow replacing methods or properties at runtime. Use subclassing, dependency injection, or test doubles if you need to intercept or mock behavior.
6. Parser Methods Should Not Mutate Node Fields After Construction
- All node fields that are
finalmust be set only in the constructor. Use thepropertiesmap for any dynamic or extensible data.
7. Keep Test Imports Canonical and Up-to-Date
- Always import node types and utility classes from their canonical files (e.g.,
model_element_node.dart,source_position.dart). - Remove imports of deleted or obsolete files.
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 · 40 lines · 0 tokens per session scan A e719a3c6a2d2
parser-and-test-consistency is a cursor rule published in the GitHub repository Consiliency/Flutter-Structurizr (7 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 527 tokens. 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 cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.