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/azam-sdet/10xquality/qa-recordergit 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/qa-recorder)<a href="https://agentmods.dev/rules/azam-sdet/10xquality/qa-recorder"><img src="https://agentmods.dev/badge/rules/azam-sdet/10xquality/qa-recorder.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.00018 | $0.02548 |
| Opus 5 | $0.00009 | $0.01274 |
| Sonnet 5 | $0.00004 | $0.00510 |
| Haiku 4.5 | $0.00002 | $0.00255 |
Grade A, and why
qa-recorder 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 5d 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 — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Recorder Agent
When the user asks to record a test, capture actions, or record UI steps, follow this protocol to watch their manual browser interactions and generate a natural language test script.
Recording Workflow
Step 1: Ask the User for Test Details
Before starting, collect:
- Target URL: Where to start recording
- Test name: A short name for the script file (e.g., "login-flow")
- Goal: What this test verifies (one sentence)
- View mode: Desktop or mobile
- Auth details (if needed): username/password
Step 2: Navigate and Start Recording
- Navigate to the target URL using Chrome DevTools MCP:
CallMcpTool: chrome-devtools → navigate_page
{ "type": "url", "url": "<target-url>" }
- If mobile view, emulate mobile viewport:
CallMcpTool: chrome-devtools → emulate
{ "viewport": { "width": 375, "height": 812, "isMobile": true, "hasTouch": true } }
- Inject the recorder script by reading
src/recorder/inject-recorder.jsand executing it viaevaluate_script:
CallMcpTool: chrome-devtools → evaluate_script
{ "function": "<contents of inject-recorder.js wrapped as IIFE>" }
- Tell the user: "Recording started. A red REC badge is visible in the browser. Go ahead and interact with the page. To mark a specific element as an assertion, hover over it and press Ctrl+Shift+A (or Cmd+Shift+A on Mac). The recorder also auto-captures toasts, alerts, modals, and page changes. When you're done, tell me to stop recording."
Step 3: Wait for the User
- The user manually clicks, types, navigates in the Chrome browser
- The injected script silently captures all interactions with enriched metadata
- Assertions are captured automatically when toasts, alerts, modals, success/error messages appear in the DOM, or when the page title or URL changes
- The user can manually mark assertions by hovering over any element and pressing Ctrl+Shift+A — a green flash confirms the capture
- The REC badge shows a running count of captured assertions (e.g., "REC | ✓ 3")
- If the user navigates to a new page (full page load), the recorder script is lost. When the user says "stop", check if the recorder is still active. If not, note that some events may have been lost after a full navigation.
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.
- 5d ago First seen · 245 lines · 18 tokens per session scan A 93134d0ed3e5
qa-recorder is a cursor rule published in the GitHub repository azam-sdet/10xquality (2 stars, last pushed 5mo ago), licensed MIT. It adds 18 tokens to every session and 2,548 once invoked, about $0.0001 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-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.
vasu-playwright-utils
../../templates/cursor-rules/vasu-playwright-utils.mdc.
playwright
本规范强制执行 Playwright 测试的最佳实践和编码标准，包括稳定的选择器、测试隔离、以用户为中心的测试和性能考虑。.
playwright
Playwright: e2e testing, page objects, fixtures, assertions.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.