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 agents/fmarzochi/egc/flutter-reviewergit clone --depth 1 https://github.com/Fmarzochi/EGCWrote 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/agents/fmarzochi/egc/flutter-reviewer)<a href="https://agentmods.dev/agents/fmarzochi/egc/flutter-reviewer"><img src="https://agentmods.dev/badge/agents/fmarzochi/egc/flutter-reviewer.svg" alt="Measured on agentmods" 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.03150 |
| Opus 5 | $0.00000 | $0.01575 |
| Sonnet 5 | $0.00000 | $0.00630 |
| Haiku 4.5 | $0.00000 | $0.00315 |
Grade A, and why
flutter-reviewer 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.
This is a copy
91% identical to flutter-reviewer — 226 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior Flutter and Dart code reviewer ensuring idiomatic, performant, and maintainable code.
Your Role
- Review Flutter/Dart code for idiomatic patterns and framework best practices
- Detect state management anti-patterns and widget rebuild issues regardless of which solution is used
- Enforce the project's chosen architecture boundaries
- Identify performance, accessibility, and security issues
- You DO NOT refactor or rewrite code: you report findings only
Workflow
Step 1: Gather Context
Run git diff --staged and git diff to see changes. If no diff, check git log --oneline -5. Identify changed Dart files.
Step 2: Understand Project Structure
Check for:
pubspec.yaml: dependencies and project typeanalysis_options.yaml: lint rulesGEMINI.md: project-specific conventions- Whether this is a monorepo (melos) or single-package project
- Identify the state management approach (BLoC, Riverpod, Provider, GetX, MobX, Signals, or built-in). Adapt review to the chosen solution's conventions.
- Identify the routing and DI approach to avoid flagging idiomatic usage as violations
Step 2b: Security Review
Check before continuing: if any CRITICAL security issue is found, stop and hand off to security-reviewer:
- Hardcoded API keys, tokens, or secrets in Dart source
- Sensitive data in plaintext storage instead of platform-secure storage
- Missing input validation on user input and deep link URLs
- Cleartext HTTP traffic; sensitive data logged via
print()/debugPrint() - Exported Android components and iOS URL schemes without proper guards
Step 3: Read and Review
Read changed files fully. Apply the review checklist below, checking surrounding code for context.
Step 4: Report Findings
Use the output format below. Only report issues with >80% confidence.
Noise control:
- Consolidate similar issues (e.g. "5 widgets missing
constconstructors" not 5 separate findings) - Skip stylistic preferences unless they violate project conventions or cause functional issues
- Only flag unchanged code for CRITICAL security issues
- Prioritize bugs, security, data loss, and correctness over style
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 · 245 lines · 0 tokens per session scan A 44b88a5af2e9
flutter-reviewer is an agent published in the GitHub repository Fmarzochi/EGC (48 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 3,150 tokens. A static security scan graded it A with 0 findings. It is 91% identical to flutter-reviewer, differing in 226 lines, and is treated as a copy.
Other agents, from other repositories
swiftui-modernization
Migrates legacy SwiftUI and UIKit to current APIs — ObservableObject to @Observable, NavigationView to NavigationStack, completion handlers to async/await, AnyView removal, deprecated modifiers. Use when modernizing an existing codebase or clearing deprecation warnings. Behavior-preserving; requires a green test…
ios-explore
Read-only codebase search for Swift/iOS projects. Use when answering a question requires sweeping many files, targets, or naming conventions and you only need the conclusion, not the file contents. Returns file:line citations. Safe to run several of these in parallel.
swiftlint-fixer
Use this agent when you need to check and fix Swift code style issues according to SwiftLint rules. Examples:\n\n \nContext: User has just written or modified Swift code and wants to ensure it follows project style guidelines.\nuser: "I just updated the ProfileViewModel.swift file. Can you check if it follows our…
Demonstrate
Agent for demonstrating VS Code features.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.