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/ndisisnd/cook/dartnpx skills add ndisisnd/cook --skill dartgit clone --depth 1 https://github.com/ndisisnd/cookWrote 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/skills/ndisisnd/cook/dart)<a href="https://agentmods.dev/skills/ndisisnd/cook/dart"><img src="https://agentmods.dev/badge/skills/ndisisnd/cook/dart.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 | $0.00050 | $0.02209 |
| Opus 5 | $0.00025 | $0.01104 |
| Sonnet 5 | $0.00010 | $0.00442 |
| Haiku 4.5 | $0.00005 | $0.00221 |
Grade A, and why
dart 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.
How it starts
The opening of the file, as written. The whole thing — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dart Standards
Priority: P0 — Language Correctness
Null Safety
- Avoid
!. Prefer local promotion, null-check patterns, and privatefinalfields. - Use
!only for documented invariants or framework/external boundaries where non-null is guaranteed but not expressible to the analyzer. - Prefer
?.,??, and null-aware patterns over forced unwrapping. AVOID lateif you need to check whether the variable was initialised — use nullable + null-check instead.DON'Texplicitly initialise variables tonull; let the type system express optionality.
Immutability
- Use
const>final>var. Use@freezedfor data classes. - Prefer
finalfor all class members. Usevaronly for locally-obvious short-lived locals. AVOIDpubliclate finalfields without initializers.
Pattern Matching (Dart 3.x)
Use switch expressions with exhaustive patterns and destructuring. Supported pattern types:
| Pattern | Example |
|---|---|
| Constant | case 42: |
| Variable | case var x: |
| Wildcard | case _: |
| Object | case Circle(radius: var r): |
| Record | case (String name, int age): |
| List | case [first, ...rest]: |
| Map | case {'key': var v}: |
| Logical-or | `case 1 |
| Guard | case var x when x > 0: |
String describe(Shape s) => switch (s) {
Circle(radius: var r) when r > 10 => 'large circle',
Circle(radius: var r) => 'circle r=$r',
Rectangle(width: var w, height: var h) => '${w}x$h rect',
};
Records
- Use records for returning multiple values:
(String, int). - Use named fields for clarity beyond two elements:
({String name, int age}).
Class Modifiers (Dart 3.x)
Choose the right modifier to express API intent explicitly:
| Modifier | Extends outside lib | Implements outside lib | Use for |
|---|---|---|---|
sealed |
no | no | Exhaustive domain state (enables exhaustive switch) |
final |
no | no | Closed hierarchy — no extension or implementation |
base |
yes | no | Allow inheritance, prevent external implementation |
interface |
no | yes | Pure contracts — implementation only |
What ships with it
3 files 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 · 224 lines · 50 tokens per session scan A 28a4c77aea69
dart is a skill published in the GitHub repository ndisisnd/cook (2 stars, last pushed 24d ago), licensed MIT. It adds 50 tokens to every session and 2,209 once invoked, about $0.0003 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 skills, from other repositories
wechat-article-writer
公众号/自媒体全流程。根据用户表述自动匹配：撰写文章、封面图、正文插图、风格提取。支持多种写作风格。当用户提到写公众号、技术博客、公众号封面、正文插图、步骤图、演示图、流程示意、分析写作风格、克隆文风、模仿爆款、提取风格时使用。详见 reference 目录。.
pre-landing-review
Pre-landing PR review. Analyzes diff against the base branch for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues. Use when explicitly asked for the specialized pre-landing workflow. Product /review requests are handled by BitFun's unified Review mechanism instead.…
miniapp-dev
Develops, maintains, and generates BitFun MiniApps (Zero-Dialect Runtime). Use when (1) working on miniapp framework code under src/crates/assembly/core/src/miniapp/ or src/web-ui/src/app/scenes/miniapps/; or (2) generating / creating / designing a NEW MiniApp for the user — including any request like "做一个小应用 / 生成…
vibe-research
Deep research and market validation for app ideas. Use when starting a new project, validating an idea, or when the user says "research my idea", "validate my app", or "help me start a new project".
commit-push-pr
Commit selected local changes, push the branch, and create or update a GitHub pull request with BitFun attribution. Use when the user asks to 提交 PR、提代码、commit and push、开 PR、create a pull request, or wants a Claude Code-like one-command PR publishing flow from BitFun.
investigate
Systematic debugging with root cause investigation. Four phases: investigate, analyze, hypothesize, implement. Iron Law: no fixes without root cause. Use when asked to "debug this", "fix this bug", "why is this broken", "investigate this error", or "root cause analysis". Proactively invoke this skill (do NOT debug…