ai CLAUDE.md

A project instruction file for FlutterSDK AI, a registry that distributes coding skills, tool connections, and commands for several developer assistants. It describes the project structure, supported components, and maintenance commands.

In plain words
What is it for?
Use it when working on the FlutterSDK AI registry, its skills, its tool server, or its installation scripts. It helps with builds, tests, linting, registry validation, and dry-run installations.
Why use it?
It gives contributors the rules needed to build, test, lint, validate, and install changes consistently. It also documents how the registry is organized across different coding tools.

Instructions file

Install

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.

agentmods
npx agentmods add instructions/fluttersdk/ai/claude-md
Clone the repo
git clone --depth 1 https://github.com/fluttersdk/ai
Per session 1,341 This file is loaded in full into every session.
When invoked 1,341 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.01341 $0.01341
Opus 5 $0.00671 $0.00671
Sonnet 5 $0.00268 $0.00268
Haiku 4.5 $0.00134 $0.00134

Measured 2d ago against content hash 39224dc88fc8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ai CLAUDE.md 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 2d 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.

CLAUDE.md · 78 lines

How it starts

The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE.md

FlutterSDK AI skill registry that distributes AI coding skills, MCP servers, and commands for Wind UI, Magic Framework, and more across OpenCode, Claude Code, Cursor, Gemini CLI, and VS Code Copilot.

Hosted via GitHub Pages at fluttersdk.github.io/ai/

Commands

Command Description
npm run build Compile MCP server (from mcps/fluttersdk-mcp/)
npm run lint ESLint check (MCP server)
npm test Run MCP server tests
cd mcps/fluttersdk-mcp && npm test Run bridge-specific tests
node -e "JSON.parse(require('fs').readFileSync('skills/index.json','utf8'))" Validate registry JSON
bash scripts/install.sh --dry-run Preview multi-tool installation

Architecture

  • skills/: GitHub Pages root. Each skill = <name>/SKILL.md + <name>/references/*.md
    • wind-ui/: Wind UI className system, from fluttersdk_wind
    • magic-framework/: Magic Framework IoC + Facades + ORM, from magic
    • fluttersdk-dusk/: E2E Flutter app driver via MCP, from fluttersdk_dusk
    • fluttersdk-telescope/: Runtime inspector, 9 ring buffers, from fluttersdk_telescope
    • fluttersdk-artisan/: CLI framework + stdio MCP server, from fluttersdk_artisan

Every skills/<name>/ directory is a MIRROR. Never edit a skill here. sync.yml rsyncs the upstream subtree with --delete, so a registry-only file is one sync away from deletion; that is how six hand-written wind-ui reference files disappeared before anyone noticed. Edit the skill in its upstream repo (fluttersdk/wind, magic, dusk, telescope, artisan) and let the sync deliver it.

The sync fires when an upstream publishes a release, not on every upstream push. To pull an unreleased skill fix, run the upstream repo's "Dispatch skill update to registry" workflow manually. Per-skill versions live in each SKILL.md frontmatter and in skills/index.json; do not copy them into prose here, they drift within a release cycle.

  • skills/index.json: OpenCode discovery manifest. Source of truth for file listing
  • .claude-plugin/: Plugin manifest (plugin.json) + marketplace catalog (marketplace.json)
  • mcps/: MCP servers (TypeScript, stdio transport, Zod schemas)
  • commands/: Claude Code plugin commands (flutter-test.md); auto-discovered as /fluttersdk:<name>
  • agents/: plugin subagents (flutter-reviewer.md, flutter-reviewer-deep.md); auto-discovered as fluttersdk:<name>. Plugin agents support name, description, model, effort, maxTurns, tools, disallowedTools, skills, memory, background, isolation only; hooks, mcpServers, and permissionMode are ignored for plugin-shipped agents, so do not add them
  • references/: plugin-owned reference files the skill and agents read through ${CLAUDE_PLUGIN_ROOT} (flutter-review-core.md, dart-style-core.md). Not part of any mirrored skill

Read the full file on GitHub · 78 lines

Changes

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.

  1. 2d ago First seen · 78 lines · 1,341 tokens per session scan A 39224dc88fc8

Subscribe to this mod's changes

ai CLAUDE.md is an instructions file published in the GitHub repository fluttersdk/ai (2 stars, last pushed 3d ago), licensed MIT. It adds 1,341 tokens to every session, about $0.0067 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.