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/HeeGyeong/ComposeSampleWrote 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/heegyeong/composesample/testing-guide)<a href="https://agentmods.dev/rules/heegyeong/composesample/testing-guide"><img src="https://agentmods.dev/badge/rules/heegyeong/composesample/testing-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/heegyeong/composesample/testing-guide"><img src="https://agentmods.dev/badge/rules/heegyeong/composesample/testing-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.00000 | $0.00155 |
| Opus 5.5 | $0.00000 | $0.00062 |
| Sonnet 5.5 | $0.00000 | $0.00031 |
| Haiku 4.5 | $0.00000 | $0.00015 |
Grade A, and why
testing-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
Testing Guide
Unit Tests
- Use JUnit5
- All ViewModels must have unit tests
- All UseCases must have unit tests
- Use Given-When-Then format
- Mock dependencies with Mockk library
UI Tests
- Use ComposeTestRule
- Each screen must have at least 1 UI test
- Prioritize semantics testing
- Screenshot testing recommended
Test Coverage
- Domain Layer: 90% or higher
- Data Layer: 80% or higher
- Presentation Layer: 70% or higher
Performance Testing
- Compose recomposition optimization tests
- Memory leak tests (LeakCanary)
- Frame drop monitoring
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 · 30 lines · 0 tokens per session scan A c5e81be44f9b
testing-guide is a cursor rule published in the GitHub repository HeeGyeong/ComposeSample (11 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 155 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 cursor rules, from other repositories
create-tests-swift
This guide outlines Swift testing principles and practices, focusing on creating effective unit tests for Swift code.
swift-testing-playbook
Comprehensive guide for migrating from XCTest to Swift Testing with best practices from WWDC 2024.
go
Idiomatic Go rules. Explicit error handling, interface-based design, context-first concurrency.
mockito
This guide provides definitive best practices for writing robust, maintainable, and readable unit tests using Mockito with JUnit 5, focusing on modern patterns and common pitfalls.
fix-galo
SYNTAX RULES.
python-general-coding-standards
A set of general standards for Python projects, including type hints, input checking, code style, security, web requests, background work, and tests. It also covers FastAPI-specific tasks such as CORS and authentication.