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/brunobrown/claude-flet-pluginWrote 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/brunobrown/claude-flet-plugin/flet-extension)<a href="https://agentmods.dev/commands/brunobrown/claude-flet-plugin/flet-extension"><img src="https://agentmods.dev/badge/commands/brunobrown/claude-flet-plugin/flet-extension/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/commands/brunobrown/claude-flet-plugin/flet-extension"><img src="https://agentmods.dev/badge/commands/brunobrown/claude-flet-plugin/flet-extension.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.00016 | $0.01150 |
| Opus 5 | $0.00008 | $0.00575 |
| Sonnet 5 | $0.00003 | $0.00230 |
| Haiku 4.5 | $0.00002 | $0.00115 |
Grade A, and why
flet-extension 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 9d 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/flet-extension — Create a Flet Extension
You are guiding the user through creating a Flet extension package step by step. Follow these 6 phases in order.
Before starting, ask the user what Flutter package they want to wrap and whether it's a Service (no UI) or UI Control (visual widget).
Phase 1: Planning
- Identify the Flutter package — name on pub.dev, latest version
- Determine extension type:
- Service (
ft.Service) — for SDKs, background services, platform APIs - UI Control (
ft.LayoutControl) — for widgets that render on screen
- Service (
- Review the Flutter API — key classes, methods, events, callbacks
- Plan the Python API:
- Properties (sent to Flutter)
- Methods (invoke Flutter methods)
- Events (receive from Flutter)
- Sub-modules (if complex SDK with namespaces)
- Plan type mappings — Dart types → Python types
Summarize the plan before proceeding.
Phase 2: Scaffold
Use flet-pkg CLI to generate the project skeleton:
# Auto-analyze the Flutter package (recommended)
flet-pkg create my-extension --analyze
# Or manually if flet-pkg is not available
If scaffolding manually, create:
flet-my-extension/
├── pyproject.toml
└── src/
├── flet_my_extension/
│ ├── __init__.py
│ ├── my_control.py
│ └── types.py
└── flutter/flet_my_extension/
├── pubspec.yaml
└── lib/
├── flet_my_extension.dart
└── src/
├── extension.dart
└── my_service.dart
Ensure pyproject.toml includes:
[tool.setuptools.package-data]
"flutter.flet_my_extension" = ["**/*"]
Phase 3: Review Generated Code
Check and fix the generated code:
- Type mappings — verify Dart→Python type conversions are correct
- Method names —
camel_to_snakeconversion from Dart - Invoke keys —
_invoke_method("key")must match Dart switch cases - Event names —
triggerEvent("name")→on_name: EventHandler - @ft.control name — must match
control.typeswitch in Dart - Enum values — string values that match Dart representations
- Platform validation — service-only or cross-platform?
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.
- 9d ago First seen · 144 lines · 16 tokens per session scan A 7577cd158a27
flet-extension is a command published in the GitHub repository brunobrown/claude-flet-plugin (3 stars, last pushed 4mo ago), licensed MIT. It adds 16 tokens to every session and 1,150 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 commands, from other repositories
arc-feature
Add a complete new feature domain to an existing React Native Expo project — types, API module, React Query hooks, screen, and components in one go. Use when adding a new entity like products, orders, chat, users, recipes, or any CRUD resource. Trigger when the user says 'add a feature', 'create a new screen for X'…
tanstack-query
TanStack Query (React Query) expert patterns for React Native/Expo. Use for data fetching, query keys, mutations, invalidation, optimistic updates, offline support, error handling, infinite scroll, cache management, TypeScript.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.