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/Arenukvern/mcp_flutterWrote 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/rules/arenukvern/mcp_flutter/test_guide)<a href="https://agentmods.dev/rules/arenukvern/mcp_flutter/test_guide"><img src="https://agentmods.dev/badge/rules/arenukvern/mcp_flutter/test_guide/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/rules/arenukvern/mcp_flutter/test_guide"><img src="https://agentmods.dev/badge/rules/arenukvern/mcp_flutter/test_guide.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.00230 | $0.00230 |
| Opus 5.5 | $0.00092 | $0.00092 |
| Sonnet 5.5 | $0.00046 | $0.00046 |
| Haiku 4.5 | $0.00023 | $0.00023 |
Grade A, and why
test_guide 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.
What it actually says
Test Guidelines
This guide outlines concise rules for writing and modifying tests in this project.
1. Data-Driven Structure
- Use maps (e.g.,
Map<String, ({...})>) to define test cases. - Iterate over cases with
forEachto minimize boilerplate.
2. Test Organization
- Group related tests using
group()and individual cases usingtest(). - Name tests and groups descriptively (e.g., "parses various currency formats", "formats EUR in different locales").
3. Input & Expected Outputs
- Define inputs and expected outputs clearly in your maps.
- Separate cases for different locales or edge conditions.
4. Assertions
- Use
expect()with a clearreasonto explain failures. - Assert each property (price, symbols, code) individually.
5. General Best Practices
- Keep tests self-contained and independent.
- Write concise, readable tests that are easy to update.
- Use data-driven approaches to facilitate modifications and extensions.
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 · 35 lines · 230 tokens per session scan A 4e65a1f4226e
test_guide is a cursor rule published in the GitHub repository Arenukvern/mcp_flutter (389 stars, last pushed today), licensed MIT. It adds 230 tokens to every session, about $0.0009 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-08-30.
Other cursor rules, from other repositories
validation-harness
Validation harness — interfaces, adapters, cenários E2E.
testing
Cursor rule "testing" from BlackLeg15/desafio_bloc_1, covering testing and cobertura existente.
terradart
TerraDart shared project guide.
python-code-validator
Validate generated Python at every step, not once at the end.
testing-conventions
Testing conventions and techniques for Strapi MCP plugin.
development-workflow
Cursor rule "development-workflow" from floriscornel/todo-mcp, covering development workflow for todo mcp, testing & quality assurance, commit structure, branch & pr workflow and publication & releases.