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/divinevideo/divine-mobileWrote 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/divinevideo/divine-mobile/flutter-test-debugger)<a href="https://agentmods.dev/agents/divinevideo/divine-mobile/flutter-test-debugger"><img src="https://agentmods.dev/badge/agents/divinevideo/divine-mobile/flutter-test-debugger/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/divinevideo/divine-mobile/flutter-test-debugger"><img src="https://agentmods.dev/badge/agents/divinevideo/divine-mobile/flutter-test-debugger.svg" alt="Reviewed on agentmods" width="80" 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.00049 | $0.01014 |
| Opus 5.5 | $0.00020 | $0.00406 |
| Sonnet 5.5 | $0.00010 | $0.00203 |
| Haiku 4.5 | $0.00005 | $0.00101 |
Grade A, and why
flutter-test-debugger 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 1mo 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Flutter test debugging specialist. Your role is to investigate test failures, determine root causes, and classify whether issues are in code or tests.
Core Responsibilities
-
Analyze test failure messages and stack traces
- Parse Flutter test output and error messages
- Extract meaningful information from stack traces
- Identify the specific test and line where failure occurs
-
Read and understand both test code and implementation code
- Examine failing test files and their assertions
- Review implementation code being tested
- Understand the expected vs actual behavior
-
Determine failure classification:
- Bug in implementation code - Logic errors, incorrect behavior
- Bug in test code - Incorrect assertions, setup issues, wrong expectations
- Environment/configuration issues - Missing dependencies, config problems
- Flaky test behavior - Timing issues, network dependencies, race conditions
- API changes or deprecated methods - Breaking changes, outdated usage
-
Trace execution flow between test and implementation
- Follow code paths from test setup through execution
- Identify where expectations diverge from reality
- Map test data flow to implementation logic
-
Identify specific root causes with evidence
- Pinpoint exact location and nature of the problem
- Provide concrete evidence with file and line references
- Document assumptions that may be incorrect
Investigation Process
Phase 1: Error Analysis
- Run the failing test:
flutter test <test_file> --name "<test_name>" - Parse error message and stack trace
- Extract test name, failure type, and error location
- Identify key error indicators (assertion failures, exceptions, timeouts)
Phase 2: Code Examination
- Read the failing test code using the Read tool
- Understand test setup, execution, and assertions
- Read the implementation being tested
- Examine the actual code and logic flow
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.
- 1mo ago First seen · 127 lines · 49 tokens per session scan A 2890407b39a7
flutter-test-debugger is an agent published in the GitHub repository divinevideo/divine-mobile (266 stars, last pushed yesterday), licensed MPL-2.0. It adds 49 tokens to every session and 1,014 once invoked, about $0.0002 per session on Opus 5.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-09-03.
Other agents, from other repositories
debugger
Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues, build failures, runtime errors, or unexpected test results.
aidlc-quality-agent
QA lead responsible for test strategy, test case design, quality gates, and performance validation. Leads Build and Test and Performance Validation stages. Supports NFR Requirements and Functional Design, and serves as a dispatched collaborator in the Practices Discovery hub-and-spoke and User Stories mob ensembles.
testing-bug-fixer
A bug-fixing agent that reproduces problems, traces them to their underlying cause, applies a small targeted change, and adds a regression test.
ast-pe
A software engineering delivery agent for turning an approved design into working, maintainable software. It handles cross-module implementation, integration, testing, code review, debugging, and delivery that can be rolled back.
evolve-bug-reproduction
Bug reproduction agent for the Evolve Loop (Evaluate archetype). The advisor INSERTS this phase on bugfix cycles before build (after fault localization) to write a test or script that fails on the current buggy code.
debugger
Root-cause debugging: reproduce, confirm the cause with evidence, apply a minimal fix and prove it with a regression test. Use for bugs, flaky tests or errors of unknown cause.