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/consiliency/flutter-structurizr/agents-mdgit 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.02390 | $0.02390 |
| Opus 5 | $0.01195 | $0.01195 |
| Sonnet 5 | $0.00478 | $0.00478 |
| Haiku 4.5 | $0.00239 | $0.00239 |
Grade A, and why
Flutter-Structurizr AGENTS.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 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 — 341 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md - Flutter Structurizr for AI Agents
This document provides essential information for AI agents (like Codex) working with the Dart Structurizr codebase. It's specifically structured to help agents understand the repository organization, setup process, and development workflow in an offline environment.
Development Environment Setup
Offline Setup for Codex
The repository includes a complete Flutter SDK and all dependencies for offline development in Codex:
# Run this first when starting a new Codex session
./codex_offline_setup_split.sh
This script will:
- Reassemble split archive files from
.codex/directory - Extract the complete Flutter SDK (704MB) and package cache (387MB)
- Configure the environment for offline operation
- Create wrappers for
flutteranddartcommands
Important: Use the Wrapper Commands
After setup, always use the wrapper commands to ensure offline operation:
# Use these wrapper commands
./flutter [command] # Flutter commands
./dart [command] # Dart commands
# Examples
./flutter pub get
./flutter test
./flutter analyze
./dart analyze
Troubleshooting Offline Setup
If you encounter issues with the offline setup:
# Check if setup completed successfully
test -f .codex_setup_complete && echo "Setup complete" || echo "Setup incomplete"
# Manually extract from archives if needed
cd .codex
cat flutter-sdk.tar.gz.part.* > flutter-sdk.tar.gz
tar -xzf flutter-sdk.tar.gz
cat pub-cache.tar.gz.part.* > pub-cache.tar.gz
tar -xzf pub-cache.tar.gz
Project Structure
Key Directories
lib/
├── domain/ # Pure Dart domain models
│ ├── model/ # Core model elements (Person, SoftwareSystem, etc.)
│ ├── view/ # View definitions (SystemContextView, etc.)
│ ├── parser/ # DSL parser components (being refactored)
│ ├── documentation/ # Documentation model
│ └── style/ # Styling system
├── application/ # Use cases and business logic
│ ├── workspace/ # Workspace management
│ ├── dsl/ # DSL parsing
│ └── command/ # Command pattern for undo/redo
├── infrastructure/ # External integrations
│ ├── serialization/ # JSON serialization
│ ├── persistence/ # File storage
│ └── export/ # Export facilities
├── presentation/ # Flutter UI components
│ ├── widgets/ # Reusable widgets
│ ├── pages/ # Application pages
│ ├── rendering/ # Canvas rendering
│ └── layout/ # Layout algorithms
test/ # Test suite
├── domain/ # Domain model tests
├── application/ # Application layer tests
├── infrastructure/ # Infrastructure tests
├── presentation/ # UI component tests
└── integration/ # End-to-end tests
example/ # Example applications
└── lib/ # Various example implementations
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 · 341 lines · 2,390 tokens per session scan A 2009a4edd116
Flutter-Structurizr AGENTS.md is an instructions file published in the GitHub repository Consiliency/Flutter-Structurizr (7 stars, last pushed 1mo ago), licensed MIT. It adds 2,390 tokens to every session, about $0.0120 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 instructions, from other repositories
Amarok-Hider AGENTS.md
Instructions for deltazefiro/Amarok-Hider, covering amarok, project overview, build, e2e test and agent rules.
AppClaw CLAUDE.md
Instructions for appclawhq/AppClaw, covering claude.md, what is appclaw?, build & run commands, architecture and entry point & cli modes (src/index.ts).
MobiAI-Core CLAUDE.md
Instructions for ArisGuimera/MobiAI-Core, covering mobiai — mobile development ai ecosystem, bootstrap and principles.
freetube CLAUDE.md
Instructions for leshkodev/freetube, covering claude.md, 1. what this project is, 2. non-negotiable constraints, 3. tech stack (locked) and 4. project structure.
ConsultMe CLAUDE.md
Instructions for Tarek-Bohdima/ConsultMe, covering claude.md, project context, common commands, module graph and conventions enforced by tooling.
Plonk AGENTS.md
Instructions for ostapondo/Plonk, covering agent rules, layout, adding a module, build & verify and code style.