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/unit-testing-standardsgit 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.02431 | $0.02431 |
| Opus 5 | $0.01215 | $0.01215 |
| Sonnet 5 | $0.00486 | $0.00486 |
| Haiku 4.5 | $0.00243 | $0.00243 |
Grade A, and why
unit-testing-standards 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.
This is a copy
100% identical to unit-testing-standards — 0 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 — 389 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Unit Testing Standards
APPLY: "Write my tests" queries
Testing Philosophy
Based on Adobe AEM unit testing best practices and community discussions:
Testing Framework Stack
- JUnit 5: Primary testing framework
- Mockito: Mock object creation and verification
- wcm.io AEM Mocks: Mock AEM context and services
- Apache Sling Mocks: Mock Sling abstractions
Test Structure Patterns
1. Standard Test File Organization
// ✅ REQUIRED: 1-to-1 mapping with source files
src/main/js/features/hero-marquee/hero-marquee.js
→ test/unit/features/hero-marquee/hero-marquee.test.js
// ✅ REQUIRED: Test suffix naming convention
// Allows easy identification and differentiation from source
2. Basic Test Structure
// ✅ STANDARD: Test structure pattern
describe('Hero Marquee Block', () => {
let mockEl;
beforeEach(() => {
// Setup fresh DOM for each test
document.body.innerHTML = '<div class="hero-marquee"></div>';
mockEl = document.querySelector('.hero-marquee');
});
afterEach(() => {
// Clean up DOM after each test
document.body.innerHTML = '';
});
it('should create basic structure', () => {
// Test the building blocks of functionality
init(mockEl);
expect(mockEl.querySelector('.foreground')).to.exist;
});
it('should handle missing content gracefully', () => {
// Test edge cases and error conditions
const emptyEl = document.createElement('div');
init(emptyEl);
expect(emptyEl.children.length).to.be.greaterThan(0);
});
});
3. Testing Asynchronous Block Initialization
// ✅ REQUIRED: Test async block patterns
describe('Async Block Features', () => {
it('should handle Promise.all data loading', async () => {
const mockData = { cards: [], ratings: {} };
// Mock async functions
global.fetchCards = () => Promise.resolve(mockData.cards);
global.fetchRatings = () => Promise.resolve(mockData.ratings);
await init(mockEl);
// Verify structure is created immediately (LCP optimization)
expect(mockEl.querySelector('.headline')).to.exist;
// Verify data enhancement happens after
expect(mockEl.querySelector('.cards-container')).to.exist;
});
it('should not block LCP with API failures', async () => {
// Mock API failure
global.fetchCards = () => Promise.reject(new Error('API Error'));
await init(mockEl);
// Basic structure should still exist
expect(mockEl.querySelector('.headline')).to.exist;
});
});
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 · 389 lines · 2,431 tokens per session scan A 954b923a0d49
unit-testing-standards is a cursor rule published in the GitHub repository adobecom/express-milo (6 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 2,431 tokens to every session, about $0.0122 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to unit-testing-standards, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.