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 skills/joker-x-dev/flutterkit/fkit-auditnpx skills add Joker-x-dev/FlutterKit --skill fkit-auditgit clone --depth 1 https://github.com/Joker-x-dev/FlutterKitWhat 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.00074 | $0.00562 |
| Opus 5 | $0.00037 | $0.00281 |
| Sonnet 5 | $0.00015 | $0.00112 |
| Haiku 4.5 | $0.00007 | $0.00056 |
Grade A, and why
fkit-audit 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
FKit Audit
审查原则
默认只读取、诊断和报告；只有用户明确要求修复时才修改代码。先阅读 AGENTS.md 与 docs/flutter-kit/README.md，再按发现的问题加载对应专题，避免一次读取所有文档。
使用结构化查询确认声明、调用和影响范围；使用文本搜索检查注释、硬编码、注解和路径。不要仅凭文件名、正则命中或 lint 数量断定问题。
审查维度
- 架构：Core/Feature/Routes/Bootstrap 依赖方向、单页与模块级数据边界、View/Logic/State/Binding 职责。
- UI：TDesign 组件复用、完整布局规范、主题语义、硬编码、链式扩展顺序、Obx 范围和响应式适配。
- 数据：Model/DataSource/Repository/Result/Service 链路、异常与持久化边界。
- 导航：模块 Navigator、参数/结果类型、Guard、路由唯一性和状态保持。
- 预览：页面和组件注解、Logic 注入、静态数据、真实请求风险和多屏覆盖。
- 代码质量：命名、中文文档注释、生成文件、测试覆盖、格式与分析诊断。
- 原生与资源：图标、启动页、配置源图、生成结果及平台一致性。
输出格式
- 按严重级别和影响范围排序问题，先给结论，再给文件、行号、证据和建议。
- 区分确定问题、潜在风险和文档差异；没有证据时继续调查，不写猜测性结论。
- 明确列出已检查范围、未检查范围、执行的命令和失败原因。
- 若没有问题，直接说明未发现问题，不为填充报告制造建议。
修复模式
用户要求修复时按目录或问题类型分批实施，保留已有工作区修改。每批运行最小相关验证，最后执行 flutter analyze、相关测试和 git diff --check；不要顺带修复任务外问题。
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 34 lines · 74 tokens per session scan A 24c587ac844d
fkit-audit is a skill published in the GitHub repository Joker-x-dev/FlutterKit (110 stars, last pushed 1mo ago), licensed MIT. It adds 74 tokens to every session and 562 once invoked, about $0.0004 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…