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/PackmindHub/packmindWrote 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/packmindhub/packmind/standard-e2e-writing-e2e-tests)<a href="https://agentmods.dev/rules/packmindhub/packmind/standard-e2e-writing-e2e-tests"><img src="https://agentmods.dev/badge/rules/packmindhub/packmind/standard-e2e-writing-e2e-tests/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/packmindhub/packmind/standard-e2e-writing-e2e-tests"><img src="https://agentmods.dev/badge/rules/packmindhub/packmind/standard-e2e-writing-e2e-tests.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.00150 | $0.00150 |
| Opus 5.5 | $0.00060 | $0.00060 |
| Sonnet 5.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 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
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.
- 1mo 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 (319 stars, last pushed yesterday), licensed Apache-2.0. It adds 150 tokens to every session, about $0.0006 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-08-30.
Other cursor rules, from other repositories
page-object-patterns
Page Object Model patterns for Selenium — BasePage, component objects, and fluent interfaces.
test
You are a senior test engineer.
cursor-rules
Playwright E2E testing rules for {{PROJECTNAME}}; the full skill lives in .agents/skills/playwright-e2e.
fusebase-flow-validation
Fusebase Flow validation/verification phase rules. Use when running gate checks, reviewing diffs, or verifying smoke prompts.
frontend-tests
Frontend Tests.
moodle-behat-testing
Use when writing or running Behat acceptance tests for Moodle plugins. Covers feature files, custom step definitions, tags, data generators in Background, JavaScript scenarios, and Selenium/Chromedriver setup.