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 skills add cometchat/cometchat-skills --skill cometchat-flutter-v6-testinggit clone --depth 1 https://github.com/cometchat/cometchat-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/skills/cometchat/cometchat-skills/cometchat-flutter-v6-testing)<a href="https://agentmods.dev/skills/cometchat/cometchat-skills/cometchat-flutter-v6-testing"><img src="https://agentmods.dev/badge/skills/cometchat/cometchat-skills/cometchat-flutter-v6-testing/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/skills/cometchat/cometchat-skills/cometchat-flutter-v6-testing"><img src="https://agentmods.dev/badge/skills/cometchat/cometchat-skills/cometchat-flutter-v6-testing.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.00083 | $0.01304 |
| Opus 5.5 | $0.00033 | $0.00522 |
| Sonnet 5.5 | $0.00017 | $0.00261 |
| Haiku 4.5 | $0.00008 | $0.00130 |
Grade A, and why
cometchat-flutter-v6-testing 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ground truth: kit symbols are catalog-verified against 6.1.0. Test tooling (
flutter_test,integration_test,mocktail) is standard Flutter, not CometChat API.
Companion skills (read first)
cometchat-flutter-v6-core— install, credentials,init→login→render. This skill ASSUMES it.cometchat-flutter-v6-patterns— how init/login is gated, which is what your tests have to work around.
Use this skill when
The user ASKS for tests. Building a feature does not imply writing tests (RULES.md) — do not volunteer a test suite as part of "add chat".
Prerequisites & install
flutter pub add --dev mocktail integration_test
flutter_test ships with Flutter.
Test the RIGHT boundary (the thing most people get wrong)
Do not test the UI Kit. CometChatConversations rendering a list, CometChatMessageList appending a message, receipts, typing — all CometChat's own tested surface. Asserting on the kit's internals produces slow tests that break on every kit upgrade and prove nothing about YOUR app.
Test what is yours:
| Worth testing | Why |
|---|---|
| The init/login gate | Your logic. Does a chat route stay unreachable until login resolves? |
| Navigation wiring | onItemTap pushes the right screen with the right user/group. |
| Target plumbing | The thread screen receives parentMessageId and the same user/group — the silent-never-sends trap. |
| Config selection | Prod flavour has no Auth Key; the right App ID per flavour. |
| Your own slots | Custom listItemView / subtitleView widgets render as expected. |
| Error paths | onError surfaces something to the user instead of a blank screen. |
Widget tests — the practical constraint
A CometChat widget expects an initialized, logged-in SDK. In a unit/widget test there is none, so:
- Test your screens' STRUCTURE and wiring, not the kit's rendered output. Pump your screen and assert your own widgets, callbacks, and navigation.
- Keep chat screens behind a thin seam you can substitute — a factory/builder your test can swap for a stub. This is the single change that makes a CometChat app testable.
- Do not try to "mock the UI Kit widgets" — they are concrete widgets, not injectable interfaces. Swap at YOUR seam instead.
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 Changed · -231 lines · -24 tokens per session 7fab58380d36
- 1mo ago First seen · 320 lines · 107 tokens per session scan A a92189beec45
cometchat-flutter-v6-testing is a skill published in the GitHub repository cometchat/cometchat-skills (150 stars, last pushed 5d ago), licensed MIT. It adds 83 tokens to every session and 1,304 once invoked, about $0.0003 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 skills, from other repositories
test-runner
For a code change, pick the right test tier by change surface, run apc test with baseline diff, and report only NEW reds vs baseline back to the task's acceptance criterion. Separates envblocked from SUT red so a broken machine never fails the code.
designing-tests
Designs and implements testing strategies for any codebase. Use when adding tests, improving coverage, setting up testing infrastructure, debugging test failures, or when asked about unit tests, integration tests, or E2E testing.
backend/testing-guide
A guide for writing backend tests: small unit tests, tests that check connected parts such as an API and database, and end-to-end tests that follow a complete user flow.
mobiai-android-testing
Use when writing or running tests in an Android project — unit tests, UI tests, choosing the right framework and patterns.
qa/test-strategy
A testing strategy based on the testing pyramid: many small unit tests, fewer integration tests, and a smaller set of end-to-end tests that follow real user journeys. It also defines checks for security, boundaries, permissions, and business consistency.
testing
Use when writing or reviewing Flutter/Dart tests (unit, widget, golden), fixing flaky tests, adding coverage, or choosing between unit and widget tests.