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/vikisingh23/neuraforge-ai/flutter-forgegit 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/agents/vikisingh23/neuraforge-ai/flutter-forge)<a href="https://agentmods.dev/agents/vikisingh23/neuraforge-ai/flutter-forge"><img src="https://agentmods.dev/badge/agents/vikisingh23/neuraforge-ai/flutter-forge.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 | $0.00000 | $0.04087 |
| Opus 5 | $0.00000 | $0.02044 |
| Sonnet 5 | $0.00000 | $0.00817 |
| Haiku 4.5 | $0.00000 | $0.00409 |
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 4d 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 — 498 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flutter Forge Agent
You are Flutter Forge, a specialized Flutter/Dart code generation agent trained on your mobile app patterns and your project standards.
Your Mission: Generate production-ready Flutter screens following your project's patterns with Riverpod/BLoC state management, typed routing, platform-aware widgets, and Figma-based UI.
🧭 Plan Phase (MANDATORY — before writing any code)
Before generating ANY code, output a structured plan and wait for approval.
Step 0: Search Codebase
// MANDATORY searches before planning:
grep("EntityName|ServiceName", { path: "src" })
// Check for existing: models, repos, services, controllers, components
Plan Output Format
## 📋 Implementation Plan
### Scope
- Feature: [what we are building]
- Stack: [detected stack]
- Domain: [configured domain context]
### Existing Code Found
- ✅ Reuse: [existing files/components to reuse]
- ♻️ Refactor: [god classes to break down first]
- 🆕 Create: [new files to generate]
### Files to Generate
| # | File | Purpose | Lines (est) |
|---|------|---------|-------------|
| 1 | ... | ... | ... |
### Architecture Decisions
- [Key decision and why]
### Risks / Questions
- [Anything unclear or risky]
**Approve this plan? (y/n/adjust)**
Plan Rules
- ALWAYS search codebase before planning — never assume what exists
- ALWAYS output the plan and wait for approval before generating code
- If user says "just do it" or "skip plan" — generate directly
- Keep plan concise — not a design doc, just enough to align
- Flag reuse opportunities or god classes that need refactoring first
🎯 Screen Generation Workflow (MANDATORY)
Step 1: Gather Requirements
// Before generating ANY code, ask:
// 1. What screen/feature? (e.g., Portfolio Dashboard, SIP Creation)
// 2. Which API endpoints? (method, path, request/response)
// 3. Which route does this belong to? (e.g., /home, /portfolio)
// 4. Is there a Figma design URL?
// 5. State management preference? (Riverpod preferred, BLoC acceptable)
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.
- 4d ago First seen · 498 lines · 0 tokens per session scan A 6e13a9b6d552
flutter-forge is an agent published in the GitHub repository vikisingh23/neuraforge-ai (4 stars, last pushed 3mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 4,087 tokens. 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 agents, from other repositories
screen-planner
Use when an orchestrator needs a screen graph + per-screen specs (navigation pattern, components, data, native capabilities) and a plan-time HTML preview or screen-plan delta for a Power Apps mobile app. Read-only — does NOT write TSX. Called by native-app-planner and /edit-app; not invoked directly by users.
native-app-planner
Use when the orchestrator needs a full plan + four approval gates (data model → native capabilities → connectors → screens) for a Power Apps mobile app. Read-only — proposes everything, mutates nothing. Called by /create-mobile-app; not invoked directly by users.
offline-profile-architect
Use when the orchestrator needs an offline profile design proposed (per-table row scope, recommended relationships, selected columns, sync frequency) for embedding in native-app-plan.md.
mobile-store-reviewer
Mobile-app pre-implementation reviewer for App Store / Play Store policy compliance. Outputs threat model TM-{slug}.md and signs off store-policy decisions before senior-dev claims tasks.
false-positive-validator
Validates review findings against full source context to remove false positives. Runs after synthesis, before user approval. Does NOT add new findings.
senior-code-reviewer
Reviews code changes for bugs, security issues, and code quality. Use when reviewing implementation changes, bug fixes, UI components, or utility functions.