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/divinevideo/divine-mobile/flutter-test-debuggergit 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.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.00049 | $0.01014 |
| Opus 5 | $0.00024 | $0.00507 |
| Sonnet 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 yesterday.
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.
- yesterday 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 (265 stars, last pushed today), licensed MPL-2.0. It adds 49 tokens to every session and 1,014 once invoked, about $0.0002 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-09-03.
Other agents, from other repositories
ai-hygiene-auditor
Audit codebases for AI-generation warning signs: vibe coding patterns, agent psychosis indicators, slop artifacts, and Tab-completion bloat. Specialized complement to bloat-auditor.
tester
테스트 작성 전담 에이전트. 단위/통합/E2E 테스트를 설계하고 구현하며, 커버리지 목표 달성을 책임진다.
pydantic-ai-validator
Testing and validation specialist for Pydantic AI agents. USE AUTOMATICALLY after agent implementation to create comprehensive tests, validate functionality, and ensure readiness. Uses TestModel and FunctionModel for thorough validation.
python-pytest-architect
Creates, reviews, and modernizes Python 3.11+ test suites using pytest. Expert in pytest-mock (not unittest.mock), hypothesis property-based testing, pytest-asyncio, and pytest-bdd. Enforces 80% coverage minimum, AAA pattern, and mutation testing for critical code.
test-expert-csk
Test expert. Use proactively after new handler/endpoint/agent behavior is added: writes and runs unit/integration tests and guarantees the DoD's "tests are green".
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…