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/cleydson/flutter-claude-codeWrote 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/cleydson/flutter-claude-code/flutter-testing)<a href="https://agentmods.dev/agents/cleydson/flutter-claude-code/flutter-testing"><img src="https://agentmods.dev/badge/agents/cleydson/flutter-claude-code/flutter-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/agents/cleydson/flutter-claude-code/flutter-testing"><img src="https://agentmods.dev/badge/agents/cleydson/flutter-claude-code/flutter-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.00000 | $0.06324 |
| Opus 5.5 | $0.00000 | $0.02530 |
| Sonnet 5.5 | $0.00000 | $0.01265 |
| Haiku 4.5 | $0.00000 | $0.00632 |
Grade A, and why
flutter-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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 1,026 lines · 0 tokens per session scan A a099af54af96
flutter-testing is an agent published in the GitHub repository cleydson/flutter-claude-code (53 stars, last pushed 7mo ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 6,324 tokens. 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
testing-specialist
Swift testing expert. Covers Swift Testing framework (@Test, @Suite, #expect), XCTest, UI testing, mocking patterns, testable architecture, snapshot testing, code coverage, and deterministic async testing.
testing-qa-agent-android
Expert testing and quality assurance specialist for JUnit, Espresso, Compose UI testing, MockK, test-driven development, and code coverage. Use proactively when writing tests, reviewing code for testability, or implementing TDD practices.
testing-qa-agent
Expert testing and quality assurance specialist for XCTest, UI testing, mocking strategies, test-driven development, and code coverage. Use proactively when writing tests, reviewing code for testability, or implementing TDD practices.
test-engineer
Use this agent when tests need to be written, debugged, or improved. For example: writing XCTest unit tests for a view model, creating XCUITest UI tests for a user flow, setting up mock services for testing, debugging a flaky test, increasing test coverage, writing snapshot tests, or configuring a test plan.
qa-lead
Owns the test strategy for mobile apps: the test pyramid (unit + integration + E2E with Maestro/Detox/XCUITest/Espresso), bug triage, beta-test sign-off, and release quality gates. Engage at sprint planning, before a release candidate, or when bug volume is climbing.
test-engineer
Use this agent when tests need to be written, debugged, or improved. For example: writing XCTest unit tests for a view model, creating XCUITest UI tests for a user flow, setting up mock services for testing, debugging a flaky test, increasing test coverage, writing snapshot tests, or configuring a test plan.