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/adobecom/express-miloWrote 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/adobecom/express-milo/nala-test-generation)<a href="https://agentmods.dev/rules/adobecom/express-milo/nala-test-generation"><img src="https://agentmods.dev/badge/rules/adobecom/express-milo/nala-test-generation/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/adobecom/express-milo/nala-test-generation"><img src="https://agentmods.dev/badge/rules/adobecom/express-milo/nala-test-generation.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.03752 | $0.03752 |
| Opus 5.5 | $0.01501 | $0.01501 |
| Sonnet 5.5 | $0.00750 | $0.00750 |
| Haiku 4.5 | $0.00375 | $0.00375 |
Grade A, and why
nala-test-generation 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 2mo 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.
This is a copy
100% identical to nala-test-generation — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 513 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nala E2E Test Generation Standards
APPLY: "Generate Nala tests" or "Write E2E tests" queries
Automated Nala Test Generation
Based on the Nala Testing Framework, this rule generates comprehensive end-to-end tests for AEM Edge Delivery Services blocks and pages.
Test Generation Patterns
1. Block-Level Test Structure
// ✅ STANDARD: Generated Nala test for blocks
import { test, expect } from '@playwright/test';
test.describe('[BlockName] Block Tests', () => {
test.beforeEach(async ({ page }) => {
await page.goto('/express/');
await page.waitForLoadState('networkidle');
});
test('should display core elements correctly', async ({ page }) => {
const block = page.locator('.block-name');
await expect(block).toBeVisible();
// Test headline presence and content
const headline = block.locator('h1, h2, h3').first();
await expect(headline).toBeVisible();
await expect(headline).not.toBeEmpty();
// Test CTA functionality
const cta = block.locator('.cta a, .button').first();
if (await cta.count() > 0) {
await expect(cta).toBeVisible();
await expect(cta).toHaveAttribute('href');
}
});
test('should be accessible', async ({ page }) => {
const block = page.locator('.block-name');
// Check ARIA labels and semantic structure
await expect(block.locator('h1, h2, h3')).toHaveCount(1); // One main heading
// Check keyboard navigation
await page.keyboard.press('Tab');
const focusedElement = page.locator(':focus');
await expect(focusedElement).toBeVisible();
});
test('should be responsive', async ({ page }) => {
const block = page.locator('.block-name');
// Mobile viewport
await page.setViewportSize({ width: 375, height: 667 });
await page.reload();
await expect(block).toBeVisible();
// Tablet viewport
await page.setViewportSize({ width: 768, height: 1024 });
await page.reload();
await expect(block).toBeVisible();
// Desktop viewport
await page.setViewportSize({ width: 1200, height: 800 });
await page.reload();
await expect(block).toBeVisible();
});
});
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.
- 2mo ago First seen · 513 lines · 3,752 tokens per session scan A 9394feba1ac5
nala-test-generation is a cursor rule published in the GitHub repository adobecom/express-milo (6 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 3,752 tokens to every session, about $0.0150 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to nala-test-generation, differing in 2 lines, and is treated as a copy.
Other cursor rules, from other repositories
puppeteer
This guide provides opinionated, actionable best practices for writing robust, performant, and maintainable Puppeteer scripts for web scraping, automation, and testing. It emphasizes modern patterns like page.locator() and efficient resource management.
web-pages-e2e-test-maintenance
Keep web pages end-to-end coverage current.
local-compose-db-lifecycle-for-web-tests
Keep local compose DB lifecycle ready for web tests.
cypress-e2e-testing-cursorrules-prompt-file
Cursor rule "cypress-e2e-testing-cursorrules-prompt-file" from XD3an/awesome-ai-coding-all-in-one, covering persona, auto-detect typescript usage, end-to-end ui testing focus, best practices and input/output expectations.
vasu-playwright-utils
../../templates/cursor-rules/vasu-playwright-utils.mdc.
playwright
A set of guidelines for Playwright, a tool that controls a web browser to test websites and web applications.