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 agents/timzaak/web-dev-skills/flutter-demo-acceptgit clone --depth 1 https://github.com/timzaak/web-dev-skillsWrote 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/timzaak/web-dev-skills/flutter-demo-accept)<a href="https://agentmods.dev/agents/timzaak/web-dev-skills/flutter-demo-accept"><img src="https://agentmods.dev/badge/agents/timzaak/web-dev-skills/flutter-demo-accept.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.00021 | $0.00288 |
| Opus 5 | $0.00010 | $0.00144 |
| Sonnet 5 | $0.00004 | $0.00058 |
| Haiku 4.5 | $0.00002 | $0.00029 |
Grade A, and why
flutter-demo-accept 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 4d 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
Flutter Demo Accept
读取目标项目约束、用户故事、测试文件、运行日志以及 ${CLAUDE_PLUGIN_ROOT}/guides/flutter/demo-testing.md。
必须核对：
- 测试顶部用户故事路径和 US ID 有效，角色、场景、动作与关键断言匹配验收标准。
- 使用真实 App composition root，没有 Provider/repository fake、生产账号或生产数据。
patrol doctor、Android 设备、锁定版本、实际 runner 命令和通过日志均有证据。- 环境准备/清理符合项目事实；无后端 App 不因缺少环境脚本被拒绝。
- 无真实等待、脆弱树位置 finder、跳过断言或仅断言瞬时 toast。
报告写入 .ai/quality/flutter-demo-accept-[name]-[timestamp].md，结论为 ACCEPTED | ACCEPTED_WITH_IMPROVEMENTS | REJECTED。用户故事映射无效、执行失败、Android 设备错误或缺少必要清理均为拒绝条件。未经授权不得修改测试或业务代码。
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.
- 4d ago First seen · 21 lines · 21 tokens per session scan A cf2f87d2e2ab
flutter-demo-accept is an agent published in the GitHub repository timzaak/web-dev-skills (69 stars, last pushed today), licensed Apache-2.0. It adds 21 tokens to every session and 288 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-30.
Other agents, from other repositories
codealive-context-explorer
Iterative code exploration across indexed repositories using CodeAlive semantic search, grep, artifact fetch, and relationship inspection. Use proactively when investigating a codebase question, tracing cross-service patterns, understanding architecture, debugging, or gathering context from external repos. Almost…
mobile-design-evaluator
Grades rendered mobile UI screenshots against the mobile-design rubric and returns a pass/fail verdict with element-level fixes. Dispatch it AFTER an inspection harness has rendered a screen's PNGs (e.g. SongsScreenInspection → build/outputs/roborazzi/inspect.png), especially after any @Composable edit, to close the…
android-developer
Native Android developer specializing in Kotlin, Jetpack Compose, and the AndroidX ecosystem. Detects the project's SDK levels, Kotlin/AGP versions, and UI stack (Compose or Views) before writing code. Use proactively for Android features, Compose UI, coroutines/Flow, Room/DataStore, DI, testing, and performance work.
code-reviewer
Senior Android code reviewer that evaluates changes across five dimensions — correctness, readability, architecture, security, performance. Use for thorough code review before merge.
swiftui-specialist
SwiftUI expert for complex UI implementation, custom layouts, animations, and visual polish. Use when building custom components that don't have native SwiftUI equivalents, when implementing complex animations, or when debugging layout issues that standard approaches can't solve.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.