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/project-conventions)<a href="https://agentmods.dev/rules/kequach/uniqlo-sales-alerter/project-conventions"><img src="https://agentmods.dev/badge/rules/kequach/uniqlo-sales-alerter/project-conventions/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/kequach/uniqlo-sales-alerter/project-conventions"><img src="https://agentmods.dev/badge/rules/kequach/uniqlo-sales-alerter/project-conventions.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.01033 | $0.01033 |
| Opus 5 | $0.00517 | $0.00517 |
| Sonnet 5 | $0.00207 | $0.00207 |
| Haiku 4.5 | $0.00103 | $0.00103 |
Grade A, and why
project-conventions 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 9d 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Conventions
After every change
- Run
python -m pytest tests/ --tb=shortand fix any failures before finishing — only when code insrc/ortests/was modified. Skip for documentation-only changes (README.md,CHANGELOG.md,.cursor/rules/, etc.). - Run
python -m ruff check src/ tests/and fix any lint errors — same rule: only when code was modified. - Update
CHANGELOG.mdunder the current version section for user-visible changes. The current version is theversionfield inpyproject.toml— never invent a new version number. Whenever the changelog is updated, also update the current version header's date to today's date (format:## vX.Y.Z — YYYY-MM-DD). - When fixing a bug that was introduced within the current unreleased version, do not add a new
Fixedentry — instead edit the existing changelog entry for that feature so it describes the correct final behaviour. Only document aFixedentry when the bug affected a previously released version. (If unsure whether a behaviour shipped in an earlier release, checkgit log/git tag.) - Update
README.mdwhen user-facing behaviour changes: new config options, new CLI flags, new API endpoints, changed notification format, new Docker examples, or anything a user would need to know. - When modifying
config.yaml, add or preserve comments that explain any new or changed keys and list supported option values where applicable.
Architecture
- Country capabilities: Use
config.capabilities(theCountryCapabilitiesregistry inconfig.py) for any country-specific logic. Never hardcode country checks likeif country == "ph". - Price display has three states in all notification channels:
has_known_discount=Trueanddiscount_percentage > 0-- strikethrough with percentagehas_known_discount=False-- "Sale" label (limited countries, unknown discount)has_known_discount=Trueanddiscount_percentage == 0-- just the price, no label
has_known_discountis determined by whether the item came from the sale feed (in_sale_feed), not by thepromofield.- Stock verification: Controlled by
CountryCapabilities.stock_api. Countries withstock_api="v5"trust the stock data — items where all sizes are OOS are dropped. Countries withstock_api="none"(PH, TH) skip the stock call but still fetch L2 variant data for accurate product URLs; items are never dropped. - Product URL style: Controlled by
CountryCapabilities.url_style. Countries withurl_style="display_code"(default) use/{priceGroup}?colorDisplayCode=XX&sizeDisplayCode=YYY. Countries withurl_style="code"(PH, TH) use?colorCode=COLXX&sizeCode=SMAYYYwithout a price-group path segment.build_product_urlhandles both.
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.
- 9d ago First seen · 47 lines · 1,033 tokens per session scan A 307a826732bf
project-conventions is a cursor rule published in the GitHub repository kequach/uniqlo-sales-alerter (30 stars, last pushed 20d ago), licensed MIT. It adds 1,033 tokens to every session, about $0.0052 per session on Opus 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-01.
Other cursor rules, from other repositories
use-contract-ir-factories
Use factory functions for creating ContractIR objects instead of manual object creation.
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.
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.
spec-for-ut
Unit testing is essential to ensure the reliability and stability of code, especially for React components and functions. Adhering to best practices and ensuring high test coverage is critical to maintaining a robust codebase.
unit-testing-standards
Cursor rule "unit-testing-standards" from adobecom/da-express-milo, covering unit testing standards, testing philosophy, testing framework stack, test structure patterns and 1. standard test file organization.
testing
Guide for writing pytest unit and integration tests.