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/kequach/uniqlo-sales-alerterWrote 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/kequach/uniqlo-sales-alerter/testing)<a href="https://agentmods.dev/rules/kequach/uniqlo-sales-alerter/testing"><img src="https://agentmods.dev/badge/rules/kequach/uniqlo-sales-alerter/testing.svg" alt="Measured on agentmods" 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.00507 |
| Opus 5 | $0.00000 | $0.00253 |
| Sonnet 5 | $0.00000 | $0.00101 |
| Haiku 4.5 | $0.00000 | $0.00051 |
Grade A, and why
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 7d 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 Conventions
Fixtures and helpers
- Use
sample_deal(**overrides)fromconftest.pyto buildSaleItemobjects. Never constructSaleItem(...)manually in tests. - Use
_make_email_cfg(**overrides)forEmailChannelConfigin notification tests. - Use
noop_verify()andnoop_watched_fetch()from conftest to isolate filter/check tests from stock verification. - Use the module-level
_mock_v3_empty()intest_uniqlo_client.pyfor v3 endpoint mocks.
Country configs in client tests
- Tests for
fetch_sale_productsmust use a country whoseCountryCapabilities.listing_sourcesinclude the endpoints being tested:- v5 discount only:
de/de - v5 discount + limitedOffer:
id/en - v3 + v5 mix:
th/en - sale_paths:
sg/en(withsale_pathsconfigured)
- v5 discount only:
E2E country representatives
- The e2e sweep tests one representative per distinct
CountryCapabilitiescombination (listing_sources × stock_api × url_style). Countries within the same group share identical pipeline code paths.de/de— v5_disc only, stock_api=v5, display_code URLs (covers uk, fr, es, it, be, nl, dk, se, au, in, kr)id/en— v5_disc + v5_ltd, stock_api=v5, display_code URLs (covers vn, my, us, ca, jp)ph/en— v3_disc + v3_ltd, stock_api=none, code URLsth/en— v5_ltd + v3_disc + v3_ltd, stock_api=none, code URLssg/en— v5_disc + sale_paths, stock_api=v5, display_code URLs
- When adding a new country, check if its capabilities match an existing group. If not, add a new representative to
_REPRESENTATIVE_COUNTRIESintest_e2e_html_preview.py.
Parametrize over copy-paste
- When 3+ tests follow the same pattern with different inputs, use
@pytest.mark.parametrize. - Example: SMTP error tests are parametrized, not duplicated.
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.
- 7d ago First seen · 38 lines · 0 tokens per session scan A 10ae9f901478
testing is a cursor rule published in the GitHub repository kequach/uniqlo-sales-alerter (30 stars, last pushed 17d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 507 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-09-01.
Other cursor rules, from other repositories
300-testing
Comprehensive testing guide covering unit, integration, E2E, test frameworks, patterns, and CI/CD integration.
hatch3r-testing
Coverage thresholds, mocking strategy, property-based testing, mutation-score targets, flaky test quarantine, and snapshot test discipline.
go-test
Rules for writing and modifying test files (test.go) in go-crypto-wallet.
issues-tests
Backend test conventions — QuarkusTest, REST Assured, Given, ArchUnit.
testing
Cursor rule "testing" from andersonlemesc/Oryntra, covering testes oryntra, laravel (pest), python (pytest), contract tests (laravel ↔ python) and browser/e2e.
tester
Tester role - Unit, E2E, and visual regression testing.