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/azam-sdet/10xqualityWrote 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/azam-sdet/10xquality/004-assertion-patterns)<a href="https://agentmods.dev/rules/azam-sdet/10xquality/004-assertion-patterns"><img src="https://agentmods.dev/badge/rules/azam-sdet/10xquality/004-assertion-patterns/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/azam-sdet/10xquality/004-assertion-patterns"><img src="https://agentmods.dev/badge/rules/azam-sdet/10xquality/004-assertion-patterns.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.00023 | $0.01614 |
| Opus 5.5 | $0.00009 | $0.00646 |
| Sonnet 5.5 | $0.00005 | $0.00323 |
| Haiku 4.5 | $0.00002 | $0.00161 |
Grade A, and why
004-assertion-patterns 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.
How it starts
The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Assertion Capture Patterns
Assertions are captured in two ways: automatic (MutationObserver) and manual (keyboard shortcut). This document describes detection logic and conversion rules for generating verification steps.
Auto-Assertion Detection
MutationObserver Selectors
The recorder observes DOM mutations and matches elements against these selectors to detect assertion-worthy content:
| Category | Selectors |
|---|---|
| ARIA roles | [role="alert"], [role="status"], [role="dialog"], [role="alertdialog"] |
| Toast/notification | .toast, .Toast, .Toastify, .Toastify__toast, .notification, .Notification |
| Snackbar | .snackbar, .Snackbar, .MuiSnackbar-root |
| Alert | .alert, .Alert, .MuiAlert-root |
| Modal | .modal, .Modal, .MuiModal-root, .dialog, .Dialog |
| Message classes | .success-message, .error-message, .warning-message, .info-message |
| Feedback | .feedback, .flash, .banner |
| Data attributes | [data-test*="Toast"], [data-test*="Alert"], [data-test*="Modal"], [data-test*="Snackbar"], [data-test*="Message"], [data-testid*="toast"], [data-testid*="alert"], [data-testid*="modal"], [data-testid*="snackbar"], [data-testid*="message"] |
Observer Configuration
observer.observe(document.body, {
childList: true,
subtree: true,
attributes: true,
attributeFilter: ['class', 'role', 'style', 'hidden', 'aria-hidden'],
});
- childList: Detects new nodes added to the DOM
- subtree: Watches descendants
- attributes: Detects attribute changes (e.g., class toggles that show/hide messages)
- attributeFilter: Limits observed attributes for performance
Classification Logic
When an element matches the assertion selectors, it is classified by role, class names, and text content:
| Condition | Classification |
|---|---|
role="alert" or role="alertdialog" |
alert |
role="status" |
status |
role="dialog" |
dialog |
| Class/text contains "error", "failed" | error |
| Class/text contains "success", "created", "saved" | success |
| Class/text contains "warning", "warn" | warning |
| Class/text contains "info", "notification" | info |
| Class contains "toast", "snackbar" | toast |
| Class contains "modal", "dialog" | dialog |
| Default | notification |
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 · 147 lines · 23 tokens per session scan A 37ea41b2dd66
004-assertion-patterns is a cursor rule published in the GitHub repository azam-sdet/10xquality (2 stars, last pushed 7mo ago), licensed MIT. It adds 23 tokens to every session and 1,614 once invoked, about $0.0001 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-31.
Other cursor rules, from other repositories
puppeteer
This guide provides opinionated, actionable best practices for writing robust, performant, and maintainable Puppeteer scripts for web scraping, automation, and testing. It emphasizes modern patterns like page.locator() and efficient resource management.
web-pages-e2e-test-maintenance
Keep web pages end-to-end coverage current.
local-compose-db-lifecycle-for-web-tests
Keep local compose DB lifecycle ready for web tests.
cypress-e2e-testing-cursorrules-prompt-file
Cursor rule "cypress-e2e-testing-cursorrules-prompt-file" from XD3an/awesome-ai-coding-all-in-one, covering persona, auto-detect typescript usage, end-to-end ui testing focus, best practices and input/output expectations.
vasu-playwright-utils
../../templates/cursor-rules/vasu-playwright-utils.mdc.
playwright
A set of guidelines for Playwright, a tool that controls a web browser to test websites and web applications.