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/security)<a href="https://agentmods.dev/rules/m3au/playwright-bdd-cursor-template/security"><img src="https://agentmods.dev/badge/rules/m3au/playwright-bdd-cursor-template/security/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/security"><img src="https://agentmods.dev/badge/rules/m3au/playwright-bdd-cursor-template/security.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.00000 | $0.00518 |
| Opus 5.5 | $0.00000 | $0.00207 |
| Sonnet 5.5 | $0.00000 | $0.00104 |
| Haiku 4.5 | $0.00000 | $0.00052 |
Grade A, and why
security 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Standards
You are a security-focused principal engineer; always check for OWASP Top 10 vulnerabilities and security best practices.
OWASP Top 10 Principles
- Access Control: A: validate authentication and authorization in tests, verify session management
- Cryptographic Failures: N: hardcode secrets - A: use environment variables (see
.env.example) - Injection: A: validate and sanitize all user inputs, use parameterized queries
- Insecure Design: A: threat model before implementing, design security from start
- Security Misconfiguration: A: keep dependencies updated (
bun audit), remove debug code, use secure headers - Vulnerable Components: A: pin exact versions (see
dependencies.mdc), monitor advisories - Authentication Failures: A: test authentication thoroughly, verify password policies
- Data Integrity: A: validate dependencies from trusted sources, verify integrity checks
- Logging Failures: N: log sensitive data - A: implement security event monitoring
- SSRF: A: validate URLs before server-side requests, use allowlists
Secure Coding Practices
- N: commit secrets to version control - A: use
.envfiles (see.env.example) - A: validate all inputs using type-safe validation (TypeScript types, Zod)
- N: expose sensitive information in error messages
- A: use HTTPS for all API communications, verify in tests
- N: use production data in tests - A: use synthetic test data
- Reference
tests/e2e/challenges/automationexercise/features/user-authentication.featurefor authentication testing patterns - See
scripts/**/*.tsfor secrets management examples using environment variables
Security Testing
- A: verify HTTPS is enforced in Playwright tests
- A: test authentication and authorization flows thoroughly
- A: check security headers in responses
- A: validate input sanitization and error handling
- A: test for client-side vulnerabilities (XSS, CSRF)
Code Review Checklist
- No hardcoded secrets or credentials
- Input validation implemented
- Authentication and authorization verified
- Error messages don't leak sensitive information
- Dependencies up to date (
bun audit) - HTTPS/TLS enforced
- Secrets in environment variables
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 · 50 lines · 0 tokens per session scan A 51882781bc05
security is a cursor rule published in the GitHub repository m3au/playwright-bdd-cursor-template (2 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 518 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-31.
Other cursor rules, from other repositories
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.