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/import-conflicts)<a href="https://agentmods.dev/rules/consiliency/flutter-structurizr/import-conflicts"><img src="https://agentmods.dev/badge/rules/consiliency/flutter-structurizr/import-conflicts/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/import-conflicts"><img src="https://agentmods.dev/badge/rules/consiliency/flutter-structurizr/import-conflicts.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.00000 | $0.00220 |
| Opus 5.5 | $0.00000 | $0.00088 |
| Sonnet 5.5 | $0.00000 | $0.00044 |
| Haiku 4.5 | $0.00000 | $0.00022 |
Grade A, and why
import-conflicts 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
import 'package:flutter/material.dart' hide Container, Element, View, Border; import 'package:flutter_structurizr/domain/model/model.dart' as structurizr_model;
// Use Flutter's Container Container(...) // Use domain model's Container structurizr_model.Container(...)
Import Conflict Resolution
- Always use
hidedirectives to avoid conflicts with Flutter built-ins (Container, Element, View, Border). - Use alias types (ModelElement, ModelContainer, ModelView) for domain model classes.
- Prefer Material or SizedBox over Container for UI layout when conflicts arise.
- For UI components that need to import all four, use:
import 'package:flutter/material.dart' hide Container, Element, View, Border; - For class references, use these alias types:
- ModelElement instead of Element
- ModelContainer instead of Container
- ModelView instead of View
- Replace Flutter's Container with Material or SizedBox for similar functionality.
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 · 28 lines · 0 tokens per session scan A 5f55b9bb6fd6
import-conflicts is a cursor rule published in the GitHub repository Consiliency/Flutter-Structurizr (7 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 220 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
gradle
Enforce modern Gradle build practices for Java and Android projects, focusing on Kotlin DSL, modularity, version catalogs, and performance optimizations.
compose-coroutines
Compose scroll/coroutine patterns — prevent programmatic scroll from being mistaken for user scroll, cancellation-safe flag resets.
android-viewmodel
Android ViewModel conventions — StateFlow, repository abstraction, coroutines, no LiveData.
trove-swift
Swift 6 and SwiftUI coding conventions for iOS development. Auto-activates when working with Swift files. Covers @Observable, async/await, NavigationStack, Swift Testing, and accessibility.
technical-stack
These rules guide the AI assistant when generating or modifying code in MagicTheOfflining, a React Native offline MTG deck viewer.
uts
A set of coding rules for UTS, a strongly typed language used by uni-app x to build apps for multiple platforms.