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/packmindhub/packmind/standard-e2e-writing-e2e-testsgit clone --depth 1 https://github.com/PackmindHub/packmindWhat 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.00150 | $0.00150 |
| Opus 5 | $0.00075 | $0.00075 |
| Sonnet 5 | $0.00030 | $0.00030 |
| Haiku 4.5 | $0.00015 | $0.00015 |
Grade A, and why
standard-e2e-writing-e2e-tests 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.
What it actually says
Standard: [E2E] Writing E2E tests
Writing proper E2E tests with our stack. Each feature we add should have its own spec file. :
- Always use the fixtures (testWithApi, testWithUser...) instead of the default
testof Playwright - Data which are not relevant to the test itself should be created using API
- Specify "testWithApi.use({ underFeatureFlag: true });" in the test file is the tested feature is under a feature flag.
Full standard is available here for further request: [E2E] Writing E2E tests
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 · 11 lines · 150 tokens per session scan A 33a84488d67d
standard-e2e-writing-e2e-tests is a cursor rule published in the GitHub repository PackmindHub/packmind (306 stars, last pushed 4d ago), licensed Apache-2.0. It adds 150 tokens to every session, about $0.0007 per session on Opus 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-30.
Other cursor rules, from other repositories
webdriver-management
Selenium WebDriver lifecycle management — driver factory, explicit waits, browser options, and teardown.
test-patterns
Selenium pytest test patterns — data-driven tests, fixtures, error handling, and performance checks.
page-object-patterns
Page Object Model patterns for Selenium — BasePage, component objects, and fluent interfaces.
testing-fundamentals
Core Cypress testing principles — selector strategy, smart waiting, and spec organization. Apply when writing or reviewing Cypress E2E tests.
cypress-excellence
Advanced Cypress testing patterns and best practices — custom commands, page objects, and network testing.
framework-architecture
Selenium + pytest framework architecture — configuration, fixtures, and dependency management.