Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add timzaak/web-dev-skills/plugin install t-toolsWrote 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-diagnose)<a href="https://agentmods.dev/agents/timzaak/web-dev-skills/flutter-demo-diagnose"><img src="https://agentmods.dev/badge/agents/timzaak/web-dev-skills/flutter-demo-diagnose.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.00022 | $0.00244 |
| Opus 5 | $0.00011 | $0.00122 |
| Sonnet 5 | $0.00004 | $0.00049 |
| Haiku 4.5 | $0.00002 | $0.00024 |
Grade A, and why
flutter-demo-diagnose 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 6d 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 Diagnose
报告结构和共享分类遵循 ${CLAUDE_PLUGIN_ROOT}/protocols/diagnostic-report-contract.md，并固定 runtime: flutter。
输入 testFile、runId，读取：
patrol_test/test-results/runs/<runId>/patrol-output.log- 失败测试、相关 Flutter 实现和用户故事
- 项目环境日志（存在时）
输出 .ai/diagnose/<test-stem>-<timestamp>.md，只选择一个主分类：
| problem_code | recommended_agent |
|---|---|
| TEST / DATA | flutter-demo-dev |
| FLUTTER / NATIVE | flutter-dev |
| BACKEND / AUTH | backend-dev |
| ENV | manual |
报告包含失败事实、唯一归因、证据链、最小修复入口、影响文件和整文件重跑命令。只写诊断报告，不修改代码、不重启环境。
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.
- 6d ago First seen · 27 lines · 22 tokens per session scan A 69ec9e71b249
flutter-demo-diagnose is an agent published in the GitHub repository timzaak/web-dev-skills (69 stars, last pushed yesterday), licensed Apache-2.0. It adds 22 tokens to every session and 244 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
checker
Fresh-context adversarial verification of completed work. Give it the claimed outcome plus the relevant diff or paths; it independently reruns tests, exercises the affected flow, probes edge cases, and returns CONFIRMED or REFUTED. Read-and-run only; it never plans, edits, or fixes anything.
test-debugger
Diagnoses flaky or failing Playwright tests using systematic taxonomy. Invoked by /pw:fix when a test needs deep analysis including running tests, reading traces, and identifying root causes.
integration-prober
External service integration verifier. Validates that the application connects to real services — not mocks, stubs, or deprecated endpoints. Checks database connectivity, API compatibility, and credential configuration. Read-only — produces findings, never code.
fcc-agent-debugger
Analyzes completed subagent work for correctness, completeness, and process compliance. Produces a structured DebugReport consumed by fcc-agent-fixer.
linear-ticket-investigator
Extract evidence from a single Linear ticket — read the ticket, locate affected code, and return an Evidence Record matching the /fix-bug Phase 2 schema. Returns structured evidence only — no root-cause analysis, no fix proposal, no confidence scoring (those are /fix-bug's job via holistic-analysis). Used by…
empirical-investigator
Empirical CLI and binary investigation specialist for wire capture, feature flag probing, version baseline monitoring, and responsible disclosure of reverse-engineering findings.