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/m3au/playwright-bdd-cursor-templateWrote 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/m3au/playwright-bdd-cursor-template/comments)<a href="https://agentmods.dev/rules/m3au/playwright-bdd-cursor-template/comments"><img src="https://agentmods.dev/badge/rules/m3au/playwright-bdd-cursor-template/comments/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/m3au/playwright-bdd-cursor-template/comments"><img src="https://agentmods.dev/badge/rules/m3au/playwright-bdd-cursor-template/comments.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.00208 | $0.00208 |
| Opus 5.5 | $0.00083 | $0.00083 |
| Sonnet 5.5 | $0.00042 | $0.00042 |
| Haiku 4.5 | $0.00021 | $0.00021 |
Grade A, and why
comments 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 7d 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
Comment Best Practices
When to Comment
- Explain WHY, not WHAT
- Complex business logic, non-obvious workarounds/hacks
- Document public APIs/interfaces
- Explain architectural decisions
- TODO comments without context
- Comment out code - delete it
ESLint Disable
- A: include reason when disabling rules
- A: use
eslint-disable-next-linefor specific lines - N: disable rules globally unless necessary
- N: disable multiple rules in one comment
- A: place disable comments in file where needed, not in config
Rules
- A: explain non-obvious code with comments
- N: commit commented-out code
- A: prefer self-documenting code over comments
- N: add comments that only restate what the code does (unneeded/useless comments)
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.
- 7d ago First seen · 34 lines · 208 tokens per session scan A 41244bce7059
comments is a cursor rule published in the GitHub repository m3au/playwright-bdd-cursor-template (2 stars, last pushed 7d ago), licensed MIT. It adds 208 tokens to every session, about $0.0008 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-10-25.
Other cursor rules, from other repositories
a11y-toolkit
WCAG 2.2 accessibility discipline for web markup and styles — applies while editing HTML/CSS/JSX/TSX/Vue.
shipwright
Shipwright harbour inspection and fitting-out checklist.
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.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.