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.
git clone --depth 1 https://github.com/Consiliency/Flutter-StructurizrWrote 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/rules/consiliency/flutter-structurizr/parser-test-best-practices)<a href="https://agentmods.dev/rules/consiliency/flutter-structurizr/parser-test-best-practices"><img src="https://agentmods.dev/badge/rules/consiliency/flutter-structurizr/parser-test-best-practices/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/consiliency/flutter-structurizr/parser-test-best-practices"><img src="https://agentmods.dev/badge/rules/consiliency/flutter-structurizr/parser-test-best-practices.svg" alt="Reviewed on agentmods" width="80" 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.00249 | $0.00249 |
| Opus 5.5 | $0.00100 | $0.00100 |
| Sonnet 5.5 | $0.00050 | $0.00050 |
| Haiku 4.5 | $0.00025 | $0.00025 |
Grade A, and why
parser-test-best-practices 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 1mo 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.
What it actually says
Parser Test Best Practices
AST and Parser Structure
- Use barrel files (like
ast_nodes.dart) to export related AST node types - Avoid circular dependencies in the AST node hierarchy
- Use interfaces or abstract base classes for common node functionality
- Create focused parser components with explicit interfaces
Error Reporting
- Always use the correct error reporter method for the context
- Use
reportStandardError(message, offset)instead ofreportError(message) - Include source position information for better error diagnostics
- Categorize errors by severity and type when appropriate
Mock Implementations
- Create simplified mock implementations that match interfaces exactly
- Provide factory methods for common test fixtures
- Separate parsing logic testing from AST construction
- Ensure return types match the interface exactly (e.g., Model addElement returns Model, not void)
Test Assertions
- Use flexible matchers for counts (
greaterThanOrEqualToinstead of exact equality) - Use predicate-based element presence checks when appropriate
- Create stub implementations for complex test cases to allow test suite to run
- Test parser components independently before integration
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.
- 1mo ago First seen · 35 lines · 249 tokens per session scan A 889518f985ca
parser-test-best-practices is a cursor rule published in the GitHub repository Consiliency/Flutter-Structurizr (7 stars, last pushed 3mo ago), licensed MIT. It adds 249 tokens to every session, about $0.0010 per session on Opus 5.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 cursor rules, from other repositories
use-contract-ir-factories
Use factory functions for creating ContractIR objects instead of manual object creation.
gonavi-go
A Go coding rule set for the GoNavi repository, based on common Go style guides and the project's own conventions. It covers file structure, errors, context, concurrency, logging, and tests.
workflow-level3
Defines the standard workflow for Level 3 (Intermediate Feature) tasks, guiding through comprehensive planning, targeted creative design, structured implementation, detailed reflection, and feature-specific archiving.
reflection-basic
Basic reflection format for Level 2 Simple Enhancement tasks.
rule-calling-guide
Comprehensive guide for calling VAN QA rules.
common-fixes
Utility for VAN QA common validation fixes.