Borrowing it
Nothing to install: this file belongs to divinevideo/divine-mobile. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/divinevideo/divine-mobile/main/.agents/skills/flutter-dispose-timer-test-failure/SKILL.mdgit 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/skills/divinevideo/divine-mobile/flutter-dispose-timer-test-failure)<a href="https://agentmods.dev/skills/divinevideo/divine-mobile/flutter-dispose-timer-test-failure"><img src="https://agentmods.dev/badge/skills/divinevideo/divine-mobile/flutter-dispose-timer-test-failure.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Data Exfiltration · line 113 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00086 | $0.00838 |
| Opus 5 | $0.00043 | $0.00419 |
| Sonnet 5 | $0.00017 | $0.00168 |
| Haiku 4.5 | $0.00009 | $0.00084 |
Grade A, and why
flutter-dispose-timer-test-failure 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flutter Dispose Timer Test Failure
Problem
Flutter widget tests fail with the error "A Timer is still pending even after the widget tree was disposed" when dispose() contains Future-based cleanup code.
Context / Trigger Conditions
- Test error:
A Timer is still pending even after the widget tree was disposed - Widget's
dispose()method contains:Future(() => ...)Future.delayed(...)Timer(...)orTimer.periodic(...)- Riverpod
ref.read(provider.notifier).someMethod()wrapped in Future
- Tests pass individually but fail when run together
- Error appears at end of test, not during widget interaction
Solution
Step 1: Identify the problematic code
Look for patterns like this in your widget:
// BAD: Creates pending timer that test framework detects
@override
void dispose() {
final notifier = _overlayNotifier;
if (notifier != null) {
Future(() => notifier.setSettingsOpen(false)); // <- Problem!
}
super.dispose();
}
Step 2: Move cleanup to deactivate()
Use deactivate() instead of dispose() and remove the Future wrapper:
// GOOD: Runs synchronously before widget is removed
@override
void deactivate() {
_overlayNotifier?.setSettingsOpen(false); // Direct call, no Future
super.deactivate();
}
Step 3: Understand the lifecycle difference
deactivate(): Called when widget is removed from tree, but State might be reinserteddispose(): Called when State will never build again, permanent cleanup
For most notification/provider cleanup, deactivate() is appropriate.
Verification
- Run the specific test that was failing
- Run the full test suite
- Verify no "Timer is still pending" errors
Example
Before (causes test failure):
class _SettingsScreenState extends ConsumerState<SettingsScreen> {
OverlayNotifier? _overlayNotifier;
@override
void dispose() {
final notifier = _overlayNotifier;
if (notifier != null) {
// This Future creates a pending timer!
Future(() => notifier.setSettingsOpen(false));
}
super.dispose();
}
}
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 · 115 lines · 86 tokens per session scan A 218d3dc2144d
flutter-dispose-timer-test-failure is a skill published in the GitHub repository divinevideo/divine-mobile (265 stars, last pushed today), licensed MPL-2.0. It adds 86 tokens to every session and 838 once invoked, about $0.0004 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 skills, from other repositories
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
langsmith-observability
LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.
experimental-code-coverage-local-debugger
Runs code coverage locally via Universal Test Runner (UTR) or helper scripts, mimicking LUCI trybots. Activate when CQ tryjobs fail or underreport coverage, to test local GN/recipe repairs before uploading, or to debug hermetic crashes.
adversarial-reviewer
Adversarial code review that assumes bugs exist and hunts for them. Use when asked to review code, find bugs, audit for correctness, stress-test a PR, or when someone says "tear this apart" or "what's wrong with this". Give no benefit of the doubt — every line is guilty until proven innocent.
cli-e2e
Write, modify, or debug Docker-based Composio CLI end-to-end tests under ts/e2e-tests/cli, including binary invocation, fixture isolation, output assertions, and package manifests. Use for CLI E2E test suites only; use cli-command for CLI source implementation.
ios-simulator
Verify and debug native, React Native, Expo, or Flutter apps on an iOS Simulator with agent-device. Use when an agent needs to launch an app, inspect its live UI, tap, type, scroll, validate a code change, collect failure evidence, or reproduce a workflow on an iPhone or iPad Simulator.