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/ConlinJoe/ai-platformWrote 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/conlinjoe/ai-platform/60-browser-qa)<a href="https://agentmods.dev/rules/conlinjoe/ai-platform/60-browser-qa"><img src="https://agentmods.dev/badge/rules/conlinjoe/ai-platform/60-browser-qa/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/conlinjoe/ai-platform/60-browser-qa"><img src="https://agentmods.dev/badge/rules/conlinjoe/ai-platform/60-browser-qa.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.02020 | $0.02020 |
| Opus 5.5 | $0.00808 | $0.00808 |
| Sonnet 5.5 | $0.00404 | $0.00404 |
| Haiku 4.5 | $0.00202 | $0.00202 |
Grade A, and why
60-browser-qa 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 — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Browser QA
Invocation
Playwright availability is not general authorization.
Do not run Playwright or other browser automation unless one of the following is true:
- The current task explicitly instructs browser QA / Playwright / browser inspection.
40-uiclassified the work as significant UI and a bounded Mode B visual verification pass is in scope (below).- The current task is local video frame rendering or preview for
the optional video-production capability, limited to that project's
local film page. This does not authorize application browser QA.
Application browser QA does not authorize video rendering.
Contract:
docs/contracts/features/video-production.md.
This includes Playwright test suites, targeted Playwright tests, automated browser inspection, automated screenshots, visual regression captures, browser-driven responsive checks, and browser console inspection through automation.
Do not infer general authorization from: Playwright being installed, existing browser tests, Playwright MCP or other browser MCP, screenshot tooling, a browser-QA contract, frontend or responsive code changes, this rule, a UI/design skill recommending screenshots, or previous turns that used Playwright.
Availability is also not justification for invoking a browser tool the bounded task does not need.
Vendor UI/design skills do not authorize browser automation.
Significant UI — bounded Mode B visual pass
Significant UI work (see 40-ui) authorizes proportionate rendered
visual verification of that UI only, when a real-browser capability
is available in the current environment.
That pass may:
- render the actual implementation
- inspect affected viewport classes
- inspect materially affected interaction states
- compare against the approved review comp and other supplied references when applicable
- check relevant accessibility concerns on the real UI
- when meaningful motion is involved, observe timing, easing, and interaction states in the running application (
40-ui). A static screenshot does not prove motion quality. - iterate if the rendered result exposes meaningful problems
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 Changed · +5 lines · +62 tokens per session f70eace45774
- 7d ago Changed · +8 lines · +108 tokens per session 62435f6a8db4
- 1mo ago Changed · +10 lines · +104 tokens per session c17e09a73177
- 2mo ago First seen · 234 lines · 1,746 tokens per session scan A 3308a43a7edb
60-browser-qa is a cursor rule published in the GitHub repository ConlinJoe/ai-platform (2 stars, last pushed 4d ago), licensed MIT. It adds 2,020 tokens to every session, about $0.0081 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
webrtc
Choose ordered/reliable vs unreliable per use case deliberately. Set maxRetransmits or maxPacketLifeTime (never both) for partial reliability; leave both unset only when full reliability is actually required. State sync wants reliable; real-time telemetry wants unreliable. (W3C WebRTC — RTCDataChannel /…
vasu-playwright-utils
../../templates/cursor-rules/vasu-playwright-utils.mdc.
chrome-extension-manifest-rules
Specific rules related to the Chrome extension manifest file, ensuring proper structure and content.
vla-registry
Multi-model GUI/VL registry — browser wllama grounding (ShowUI-2B is default + E2E gate).
safari
This file, safari.mdc, serves as a repository for detailed working notes, observations, and learnings acquired during the process of automating Safari interactions, particularly for the MCP Inspector UI. It's intended to capture the nuances of trial-and-error, debugging steps, and insights into what worked, what…
scrapy
Cursor rule "scrapy" from Solihatun1/AI-Cursor-Scraping-Assistant, covering scrapy best practices, 1. code organization and structure, 1.1. directory structure, 1.2. file naming conventions and 1.3. module organization.