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/vikisingh23/neuraforge-aiWrote 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/vikisingh23/neuraforge-ai/flutter-forge)<a href="https://agentmods.dev/rules/vikisingh23/neuraforge-ai/flutter-forge"><img src="https://agentmods.dev/badge/rules/vikisingh23/neuraforge-ai/flutter-forge/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/vikisingh23/neuraforge-ai/flutter-forge"><img src="https://agentmods.dev/badge/rules/vikisingh23/neuraforge-ai/flutter-forge.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.00008 | $0.00039 |
| Opus 5.5 | $0.00003 | $0.00016 |
| Sonnet 5.5 | $0.00002 | $0.00008 |
| Haiku 4.5 | $0.00001 | $0.00004 |
Grade A, and why
flutter-forge 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
Read agents/flutter-forge.md for full instructions. Follow AGENTS.md for architecture principles.
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 · 7 lines · 8 tokens per session scan A 232191142a8b
flutter-forge is a cursor rule published in the GitHub repository vikisingh23/neuraforge-ai (4 stars, last pushed 16d ago), licensed Apache-2.0. It adds 8 tokens to every session and 39 once invoked, about $0.0000 per session on Opus 5.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
code-review-checklist
A code-review checklist for 1C source files, including BSL and OS files. It groups findings by severity and checks issues such as security, performance, errors, access control, duplication, and maintainability.
language-agnostic-patterns
Language-agnostic programming patterns: SOLID, design patterns, clean code, and architecture. Load when refactoring, designing abstractions, or reviewing structure — not for everyday syntax.
mmr-review
Run multi-model code review with the MMR CLI (mmr review) before merging or finishing a change, or a multi-model design critique (mmr critique) of a design doc, plan, or proposed approach before building it. Use when the user asks to review code, a PR, a diff, or staged changes, or to critique/second-opinion a design…
mobile-cross-platform
Cross-platform mobile: Flutter, React Native, Expo. Load when editing mobile manifests, platform folders, or shared mobile architecture — not for everyday app logic.
code-review
Critérios para revisão de código (code review) em projetos React Native. Aplicar ao revisar PRs, diffs ou mudanças de código.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.