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/abhinav503/flutter-agentic/review-codegit clone --depth 1 https://github.com/abhinav503/flutter-agenticWhat 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.00021 | $0.00147 |
| Opus 5 | $0.00010 | $0.00073 |
| Sonnet 5 | $0.00004 | $0.00029 |
| Haiku 4.5 | $0.00002 | $0.00015 |
Grade A, and why
review-code 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 yesterday.
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
Run after any AI-generated code to catch rule violations before committing.
If no files were specified, ask: "Which files or feature should I review?"
Read the project rules in this order before checking anything:
docs/ai-rules/conventions.md— forbidden patterns and build rulesdocs/reference/architecture.md— layer boundaries, naming, DI, error flow, testing
Then audit the specified files against every check in docs/how-to/review-code.md
and report a ✅/❌ checklist. Offer to fix each violation after reporting.
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.
- yesterday First seen · 16 lines · 21 tokens per session scan A a9b284a6b68c
review-code is a cursor rule published in the GitHub repository abhinav503/flutter-agentic (10 stars, last pushed 9d ago), licensed MIT. It adds 21 tokens to every session and 147 once invoked, about $0.0001 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
blog-guide
Writing guides for the FlutterInit blogs (Guides category).
flutter
Flutter and coding-agent rules for flutter-agentic-starter.
intentflow
IntentFlow architecture rules for iOS features.
project-core
Invariantes globais do laboratório Flutter + validation harness.
flutter-app
Convenções do app Flutter (lib/).
git-commit-attribution
Git commits must use the human developer identity only; never Cursor Agent co-authorship.