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-test-best-practicesgit 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.00249 | $0.00249 |
| Opus 5 | $0.00125 | $0.00125 |
| Sonnet 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 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.
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.
- 2d 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 1mo ago), licensed MIT. It adds 249 tokens to every session, about $0.0012 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 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.