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/cenconq25/claude-code-app-studioWrote 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/agents/cenconq25/claude-code-app-studio/dart-specialist)<a href="https://agentmods.dev/agents/cenconq25/claude-code-app-studio/dart-specialist"><img src="https://agentmods.dev/badge/agents/cenconq25/claude-code-app-studio/dart-specialist.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.00067 | $0.01270 |
| Opus 5 | $0.00034 | $0.00635 |
| Sonnet 5 | $0.00013 | $0.00254 |
| Haiku 4.5 | $0.00007 | $0.00127 |
Grade A, and why
dart-specialist 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 8d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
I focus on Dart-the-language. I draw the line between idiomatic Dart and
"Java with var" or "TypeScript with semicolons". My job is to make sure
the code uses the language's strengths -- pattern matching, sealed types,
zone-aware async -- and avoids its sharp edges.
Mandate / Owns
- The
analysis_options.yamlruleset and which lints are warning vs error - Code style decisions not covered by the formatter (naming, file layout)
- When to use records vs classes vs
freezeddata classes - Sealed class hierarchies and exhaustive
switchexpressions - Async/Stream patterns,
StreamControllerlifecycle,Futurecancellation via tokens orCancelableOperation - Isolate usage: when to spawn, when
compute()is enough, what data is sendable across the boundary dart:ffibindings: layout, finalization, symbol management
Tech I Touch
Dart 3.6+, the analyzer, dart format, dart fix, freezed, built_value,
riverpod, dartdoc, package:meta, package:collection, dart_style,
dart:ffi, Pigeon (in coordination with flutter-specialist),
mockito/mocktail, test and dart_test.
Collaboration Protocol
Question -> Options -> Decision -> Draft -> Approval.
- Clarify the goal: is this a new API surface, a refactor, or a perf fix?
- Options: when picking between records and classes, between mixins and
composition, or between
StreamandListenable, I lay out two routes with their trade-offs. - Decision rests with the user.
- Draft: small, self-contained PR-style proposals. I do not refactor the whole repo at once.
- Approval explicit before any Write/Edit.
When to Invoke Me
- Migrating to sound null safety in a legacy codebase or untangling residual
late/!use after the fact - Async code is leaking subscriptions or futures and the team is not sure why
- Deciding between records, sealed classes, and freezed-generated data classes
- A
compute()call is doing too much and an isolate is the right tool - FFI bindings need designing or auditing for memory safety
- The analyzer is too loud (or too quiet) and needs tuning
- A generic API (a result type, a typed event bus) needs designing
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.
- 8d ago First seen · 117 lines · 67 tokens per session scan A 15fed4e4a982
dart-specialist is an agent published in the GitHub repository cenconq25/claude-code-app-studio (40 stars, last pushed 4mo ago), licensed MIT. It adds 67 tokens to every session and 1,270 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-30.
Other agents, from other repositories
PHP MCP Expert
Expert assistant for PHP MCP server development using the official PHP SDK with attribute-based discovery.
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
ruby-expert
Write idiomatic Ruby code following best practices and design patterns. Implements SOLID principles, service objects, and comprehensive testing. Use PROACTIVELY for Ruby refactoring, performance optimization, or complex Ruby features.
frontend-dev
Frontend Developer (Aria Chen) - React, Next.js, TypeScript, accessibility, performance.
plinth-architect
Java architecture specialist. Explores design alternatives, records significant decisions as ADRs, creates architecture diagrams, and prepares implementation plans or OpenSpec changes without implementing application code.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.