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 commands/christopherlouet/claude-base/dev-fluttergit clone --depth 1 https://github.com/christopherlouet/claude-baseWrote 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/christopherlouet/claude-base/dev-flutter)<a href="https://agentmods.dev/commands/christopherlouet/claude-base/dev-flutter"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/dev-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.00000 | $0.00389 |
| Opus 5 | $0.00000 | $0.00195 |
| Sonnet 5 | $0.00000 | $0.00078 |
| Haiku 4.5 | $0.00000 | $0.00039 |
Grade A, and why
dev-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 3d 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
DEV-FLUTTER Agent
Create Flutter widgets, screens and features with Clean Architecture.
Request context
$ARGUMENTS
Goal
Develop Flutter components (simple widget, screen with BLoC, complete feature) following Clean Architecture (data/domain/presentation) with tests.
Workflow
- Define the component type (simple Widget, Screen, complete Feature)
- Identify the needs: props, state management (BLoC/Cubit), API integration, animations
- For a widget: create the widget with a
constconstructor, typed and documented props - For a screen: implement BLoC (sealed events, sealed states, bloc with usecases)
- For a complete feature: data layer (datasources, models, repository impl), domain (entities, repository interface, usecases), presentation (bloc, pages, widgets)
- Handle the 4 states (loading, error, empty, data) with
switchexpressions - Integrate the API (Supabase, GraphQL or REST) via datasources
- Write the tests (widget tests + BLoC tests)
- Configure navigation (GoRouter) with auth redirect
Expected output
Generated files according to the type (widget + test, or complete feature with all layers), documentation with usage and props.
Related agents
| Agent | When to use it |
|---|---|
/dev:dev-supabase |
Supabase backend configuration |
/dev:dev-api |
GraphQL/REST integration |
/qa:qa-mobile |
Mobile performance and accessibility audit |
/dev:dev-tdd |
Complementary tests |
IMPORTANT: Always use const constructors to optimize rebuilds.
YOU MUST separate business logic from presentation (Clean Architecture).
NEVER put business logic in widgets - use BLoC/UseCases.
Think hard about widget reusability before coding.
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.
- 3d ago First seen · 48 lines · 0 tokens per session scan A b5df2c376ab0
dev-flutter is a command published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 389 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-09-03.
Other commands, from other repositories
e2e
Create and run E2E tests across web, mobile, and desktop with auto-detection and CLI-first toolchains.
run
Implement SPEC requirements using DDD/TDD methodology.
test-plan
Generate a test strategy document — test matrix, coverage goals, and test pyramid allocation for the current project.
test-suite
Run comprehensive test suite with coverage analysis.
deps-update
Audit and update dependencies safely.
journey-audit
Outside-in product audit as a deep session — 7 read-only roles check what the site promises against what the code does, what a user experiences, what arrives by mail, and what the data says is used. Writes a dossier; needs a per-repo journey-manifest.