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/tugkanboz/awesome-cursorrules/test-patternsgit clone --depth 1 https://github.com/tugkanboz/awesome-cursorrulesWhat 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 | $0.00000 | $0.02177 |
| Opus 5 | $0.00000 | $0.01089 |
| Sonnet 5 | $0.00000 | $0.00435 |
| Haiku 4.5 | $0.00000 | $0.00218 |
Grade A, and why
test-patterns 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 2d 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 — 271 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Selenium Python Test Patterns
Advanced Test Structure
- Arrange-Act-Assert Pattern: Clear test structure with setup, action, and verification
- Data-Driven Testing: Parametrized tests with comprehensive data coverage
- Test Categorization: Smart use of pytest markers for test organization
- Robust Error Handling: Graceful failure management and recovery
Data-Driven Test Excellence
import pytest
from pages.login_page import LoginPage
from pages.dashboard_page import DashboardPage
class TestUserAuthentication:
"""Comprehensive user authentication test suite."""
@pytest.mark.smoke
@pytest.mark.parametrize("user_type,expected_dashboard", [
("admin", "admin-dashboard"),
("manager", "manager-dashboard"),
("employee", "employee-dashboard"),
("guest", "guest-dashboard")
])
def test_role_based_dashboard_access(self, driver, test_data, user_type, expected_dashboard):
"""Test that users see appropriate dashboard based on their role."""
# Arrange
user_credentials = test_data.get_user_credentials(user_type)
login_page = LoginPage(driver)
# Act
dashboard_page = login_page.navigate() \
.login(user_credentials['email'], user_credentials['password'])
# Assert
assert dashboard_page.is_loaded(), f"Dashboard not loaded for {user_type}"
assert dashboard_page.get_dashboard_type() == expected_dashboard, \
f"Wrong dashboard type for {user_type}"
assert dashboard_page.get_user_role() == user_type.upper(), \
f"User role not displayed correctly"
@pytest.mark.regression
@pytest.mark.parametrize("invalid_credential", [
{"email": "[email protected]", "password": "validPassword123", "error": "Invalid email"},
{"email": "[email protected]", "password": "wrongPassword", "error": "Invalid password"},
{"email": "", "password": "validPassword123", "error": "Email is required"},
{"email": "[email protected]", "password": "", "error": "Password is required"},
{"email": "notanemail", "password": "validPassword123", "error": "Invalid email format"}
])
def test_login_validation_errors(self, driver, invalid_credential):
"""Test comprehensive login validation error scenarios."""
# Arrange
login_page = LoginPage(driver)
# Act
result_page = login_page.navigate() \
.login(invalid_credential['email'], invalid_credential['password'])
# Assert
assert isinstance(result_page, LoginPage), "Should remain on login page for invalid credentials"
assert result_page.get_error_message() == invalid_credential['error'], \
f"Expected error: {invalid_credential['error']}"
assert result_page.is_password_field_cleared(), "Password field should be cleared after error"
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.
- 2d ago First seen · 271 lines · 2,177 tokens per session scan A 6eaeb61f3086
test-patterns is a cursor rule published in the GitHub repository tugkanboz/awesome-cursorrules (20 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,177 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-30.
Other cursor rules, from other repositories
cursorrules
You are building an AI/ML project with Python. The project uses PyTorch for model training, handles data pipelines with proper validation, tracks experiments systematically, and follows production ML engineering practices. Code is type-hinted, tested, and reproducible.
unity-input
Guidelines for working with the New Input System in Unity 6.2.
unity-ui
Assets/ ├── UI/ │ ├── Runtime/ │ │ ├── Controllers/ │ │ │ └── MainMenuController.cs │ │ ├── Views/ │ │ │ └── MainMenuView.cs │ │ ├── ViewModels/ │ │ │ └── HealthViewModel.cs │ │ ├── UXML/ │ │ │ └── MainMenu.uxml │ │ └── USS/ │ │ └── MainMenu.uss │ └── Editor/ │ └── UIBuilderExtensions.cs.
java
Modern Java: records, sealed classes, streams, virtual threads.
javascript
Modern JavaScript: ES2023+, async patterns, common traps.
accessibility
Accessibility: semantic HTML, ARIA, keyboard navigation, testing.