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/commits)<a href="https://agentmods.dev/rules/m3au/playwright-bdd-cursor-template/commits"><img src="https://agentmods.dev/badge/rules/m3au/playwright-bdd-cursor-template/commits/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/commits"><img src="https://agentmods.dev/badge/rules/m3au/playwright-bdd-cursor-template/commits.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.00471 |
| Opus 5.5 | $0.00000 | $0.00188 |
| Sonnet 5.5 | $0.00000 | $0.00094 |
| Haiku 4.5 | $0.00000 | $0.00047 |
Grade A, and why
commits 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.
What it actually says
Conventional Commits
Follow Conventional Commits specification.
Scope Examples
Use lowercase, kebab-case: playwright, page-objects, config, docs, tests
Examples
See git history for real examples. Common patterns: feat:, feat(scope):, fix(scope): with body explaining non-obvious changes.
Commit Types and Gitmojis
All commit types are mapped to gitmojis for display in version bumping logs. Mappings follow the gitmoji.dev specification:
feat✨ - Introduce new featuresfix🐛 - Fix a bugdocs📝 - Add or update documentationstyle🎨 - Improve structure / format of the coderefactor♻️ - Refactor codetest✅ - Add, update, or pass testschore🔨 - Add or update development scriptsperf⚡ - Improve performanceci👷 - Add or update CI build systembuild📦 - Add or update compiled files or packagesrevert⏪ - Revert changes
Note: Gitmojis are for display purposes only in version bumping logs. Commit messages must still follow Conventional Commits format without emojis:
type(scope): subject
Rules
- A: use lowercase for type and scope
- A: use imperative mood in subject
- N: end subject with period
- A: explain non-obvious changes in body
- A: reference related issues in footer
- A: commit by logical units - group related changes together (e.g., all husky hooks, all docs, all configs)
- A: amend commits when making follow-up fixes to the same change (typos, lint errors, formatting)
- Version bumping is automatic: feat = minor, fix/perf/refactor = patch, BREAKING CHANGE = major
- Changelog generation is automatic
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 · 47 lines · 0 tokens per session scan A 68a45cc7ff03
commits is a cursor rule published in the GitHub repository m3au/playwright-bdd-cursor-template (2 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 471 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
boatswain
Boatswain hygiene, recheck, and local commit checklist.
003-attribution
Prohibits AI attribution strings in commits, PR bodies, code comments, and client-facing content.
no-ai-contributors
Never add AI tools as git authors or project contributors.
git-discipline
Commit, push, and branching rules. Owns ALL git behavior; other files state only their deviations.
git-commit-standards
Enforce structured Git commit messages.
git
Cursor rule "git" from duongductrong/cursor-kit, covering git conventions, commit messages, types, subject rules and examples.