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/adobecom/express-milo/nala-test-generationgit clone --depth 1 https://github.com/adobecom/express-miloWhat 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.03752 | $0.03752 |
| Opus 5 | $0.01876 | $0.01876 |
| Sonnet 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 3d 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.
- 3d 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.0188 per session on Opus 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
maestro-device-selection
Maestro tests can run on either iPhone or iPad simulators based on tags in the test YAML files. This allows you to test iPad-specific UI layouts and features while maintaining a single test suite.
webdriver-management
Selenium WebDriver lifecycle management — driver factory, explicit waits, browser options, and teardown.
local-compose-db-lifecycle-for-web-tests
Keep local compose DB lifecycle ready for web tests.
cypress-e2e-testing-cursorrules-prompt-file
Cursor rules for Cypress development with E2E testing.
vasu-playwright-utils
../../templates/cursor-rules/vasu-playwright-utils.mdc.
laravel-testing
Laravel testing strategy — Pest first, Playwright for UI.