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/loulanyue/awesome-claude-notesWrote 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/loulanyue/awesome-claude-notes/flutter-reviewer)<a href="https://agentmods.dev/agents/loulanyue/awesome-claude-notes/flutter-reviewer"><img src="https://agentmods.dev/badge/agents/loulanyue/awesome-claude-notes/flutter-reviewer/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/agents/loulanyue/awesome-claude-notes/flutter-reviewer"><img src="https://agentmods.dev/badge/agents/loulanyue/awesome-claude-notes/flutter-reviewer.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.00050 | $0.03198 |
| Opus 5 | $0.00025 | $0.01599 |
| Sonnet 5 | $0.00010 | $0.00640 |
| Haiku 4.5 | $0.00005 | $0.00320 |
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 10d 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 — 18 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 — 251 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 rulesCLAUDE.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.
- 10d ago First seen · 251 lines · 50 tokens per session scan A 8c1a9d4f572c
flutter-reviewer is an agent published in the GitHub repository loulanyue/awesome-claude-notes (270 stars, last pushed 6d ago), licensed MIT. It adds 50 tokens to every session and 3,198 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to flutter-reviewer, differing in 18 lines, and is treated as a copy.
Other agents, from other repositories
ai_slop_reviewer
Expert code auditor that detects AI-generated code quality defects, hallucinated patterns, and structural anti-patterns across any codebase.
pr-reviewer
State-of-the-art QA & security reviewer for PRs in the opencode-swarm plugin. Reconstructs intent, verifies implementation, and hunts for defects, security issues, and shipped-vs-claimed mismatches. Operates read-only. Never approves without positive evidence. Never invents repository facts.
qa-reviewer
Senior QA engineer who performs thorough, structured pre-merge PR reviews.
night-reviewer
Night/branch review gate (shell-out to Codex Sol). Read-only. Not the daytime adoc writer.
flutter-developer
Flutter/Dart cross-platform development, Riverpod state management, and platform channels specialist. Use when building Flutter apps, implementing state management, or working with native platform features. Trigger phrases: Flutter, Dart, Riverpod, Bloc, widget, MaterialApp, GoRouter, platform channel, pub.dev, build…
mobile-release-manager
App store submissions, mobile CI/CD, ASO, code signing, and beta distribution specialist. Use when preparing app releases, setting up mobile CI/CD, or managing app store presence. Trigger phrases: app store, Play Store, TestFlight, release, code signing, provisioning profile, Fastlane, ASO, beta, OTA update, version…