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.
npx agentmods add rules/featurefactory-io/mimir/do-semantic-versioning-on-ui-elementsgit clone --depth 1 https://github.com/FeatureFactory-io/mimirWhat 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 | $0.00000 | $0.00269 |
| Opus 5 | $0.00000 | $0.00134 |
| Sonnet 5 | $0.00000 | $0.00054 |
| Haiku 4.5 | $0.00000 | $0.00027 |
Grade A, and why
do-semantic-versioning-on-ui-elements 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 3d 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
UI naming for Playwright and accessibility
Selector order (use in this order): get_by_test_id → get_by_role → get_by_label → get_by_text (stable only). Do not use CSS/XPath for primary flows.
Every interactive control: stable data-testid, plus aria-label or visible label; forms need Label + aria-describedby for errors; dialogs need unique accessible name.
Naming: hierarchical feature-area--role, e.g. intent-form-dialog, intent-name-input, save-intent-button. Lists/cards: container + per-item ids (data-intent-id).
State: expose data-state, data-valid, aria-invalid, aria-pressed where it affects tests.
Portals (dialogs/menus): query from page, not a nested container—page.get_by_test_id("…").
Tests: disable animations in test env (1ms transitions). Prefer stable data-testid over dynamic button text.
Checklist before merge: ids on interactive nodes; labels on inputs; dialog names; no CSS-only E2E selectors; portals from page.
See project E2E docs for full examples when needed.
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.
- 3d ago First seen · 22 lines · 0 tokens per session scan A 21af6510cfb9
do-semantic-versioning-on-ui-elements is a cursor rule published in the GitHub repository FeatureFactory-io/mimir (13 stars, last pushed 5d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 269 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
maestro-device-selection
Maestro tests can run on either iPhone or iPad simulators based on tags in the test YAML files. This allows you to test iPad-specific UI layouts and features while maintaining a single test suite.
webdriver-management
Selenium WebDriver lifecycle management — driver factory, explicit waits, browser options, and teardown.
local-compose-db-lifecycle-for-web-tests
Keep local compose DB lifecycle ready for web tests.
cypress-e2e-testing-cursorrules-prompt-file
Cursor rules for Cypress development with E2E testing.
vasu-playwright-utils
../../templates/cursor-rules/vasu-playwright-utils.mdc.
laravel-testing
Laravel testing strategy — Pest first, Playwright for UI.