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/sairam0424/MindForgeWrote 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/commands/sairam0424/mindforge/flutter)<a href="https://agentmods.dev/commands/sairam0424/mindforge/flutter"><img src="https://agentmods.dev/badge/commands/sairam0424/mindforge/flutter.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.00029 | $0.00502 |
| Opus 5 | $0.00015 | $0.00251 |
| Sonnet 5 | $0.00006 | $0.00100 |
| Haiku 4.5 | $0.00003 | $0.00050 |
Grade A, and why
mindforge:flutter 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.
What it actually says
<execution_context> @.mindforge/skills/flutter-architecture/SKILL.md </execution_context>
-
Widget Architecture: Composition over inheritance. Extract reusable widgets. Use const constructors (performance win). Separate stateful logic from UI. Keys for list performance. Avoid deep widget trees (>10 levels).
-
Platform Channels: Method channels for one-time calls. Event channels for streams. Use pigeon for type-safe codegen. Handle threading (iOS main thread requirement). Implement proper error handling across boundary.
-
Performance: Use ListView.builder (lazy loading). DevTools for widget rebuild analysis. Avoid setState in loops. Use RepaintBoundary strategically. Profile with Observatory. Target 60fps (120fps on ProMotion).
-
Code Generation: Freezed for immutable models. json_serializable for JSON parsing. built_value for value objects. auto_route for type-safe navigation. Run build_runner watch during development.
-
Testing: Unit tests (business logic). Widget tests (UI components). Integration tests (full app flows). Golden tests (pixel-perfect UI). Mock platform channels. Aim for >80% coverage.
-
Release: Obfuscate Dart code. Minimize app size (tree-shaking, deferred loading). Configure ProGuard rules. Test on min SDK version. Set up code push (Shorebird) for hotfixes.
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 · 38 lines · 29 tokens per session scan A 0e3aee46d409
mindforge:flutter is a command published in the GitHub repository sairam0424/MindForge (0 stars, last pushed 4d ago), licensed MIT. It adds 29 tokens to every session and 502 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-09-03.
Other commands, from other repositories
toh-mobile
Turn the current web app into a mobile app — PWA (default) or native store build (Capacitor).
p0-regulatory
Identifies regulatory requirements, DSGVO (GDPR) obligations, and legal knock-out criteria early on, before significant time is invested in the idea. A regulatory showstopper should be recognised as early as possible.
p3-infra-monitoring
Defines logging, metrics, alerting and error tracking.
p3-infra-teststrategy
Defines test levels, test tools, coverage targets and critical test paths.
sdd
Spec-driven dev loop. Plan once, then dev↔test↔eval loop until PRP spec satisfied. Local only, no PR.
continue
Resume the active pipeline at the next pending stage.