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/usrrname/cursorrules/testing-pyramid-agentgit clone --depth 1 https://github.com/usrrname/cursorrulesWhat 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.00000 | $0.02198 |
| Opus 5 | $0.00000 | $0.01099 |
| Sonnet 5 | $0.00000 | $0.00440 |
| Haiku 4.5 | $0.00000 | $0.00220 |
Grade A, and why
testing-pyramid-agent 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 291 lines — stays where its author put it; the contents beside it link to each section on GitHub.
actions:
-
type: suggest message: | To analyze test distribution, first identify the test framework and check for coverage commands:
- Check package.json for test framework dependencies (jest, vitest, playwright, cypress, mocha)
- Look for coverage scripts in package.json scripts section (test:coverage, coverage, etc.)
- Use the framework's list command to identify test files:
- Jest:
npx jest --listTests - Vitest:
npx vitest list - Playwright:
npx playwright test --list - Cypress: Check cypress.config.js for test patterns
- Jest:
Then classify tests by:
- File path (e2e/, integration/, unit/)
- Content keywords (mock, playwright, cypress, database, etc.)
- Test framework indicators
Target distribution: 70% unit, 20% integration, 10% E2E
examples:
-
description: "Unit Test Example" input: | // Bad: Testing multiple units together test('process user data', () => { const result = processUserData(validateUser(createUser(data))); expect(result).toBe(expected); }); output: | // Good: Testing single unit with clear arrangement describe('User Processing', () => { it('should process valid user data correctly', () => { // Arrange const mockUser = createMockUser();
// Act const result = processUserData(mockUser); // Assert expect(result).toEqual(expected); });});
-
description: "Integration Test Example" input: | // Bad: Testing everything in one E2E test test('user workflow', async () => { await createUser(); await loginUser(); await updateProfile(); await deleteUser(); }); output: | // Good: Focused integration test describe('User Authentication Integration', () => { it('should successfully authenticate valid user', async () => { // Arrange const user = await createTestUser();
// Act const result = await authService.authenticate(user.credentials); // Assert expect(result.authenticated).toBe(true); });});
-
description: "E2E Test Example" input: | // Bad: Testing minor features end-to-end test('user can change avatar', async () => { await page.goto('/profile'); await page.click('#avatar'); await page.upload('#file-input', 'test.jpg'); await expect(page.locator('#avatar')).toHaveAttribute('src', /test/); }); output: | // Good: E2E test for critical user journey describe('Critical User Journey', () => { it('should allow user to complete checkout process', async () => { // Arrange await loginAsTestUser(); // Act await navigateToProducts(); await addItemToCart(); await proceedToCheckout(); await fillShippingDetails(); await completePayment();
// Assert await expect(page.locator('#order-confirmation')).toBeVisible(); });});
tests:
-
input: | // Single test file with no structure test('it works', () => { expect(true).toBe(true); }); output: | describe('Feature Module', () => { describe('Unit Tests', () => { it('should handle valid input correctly', () => { // Arrange const input = validTestData(); // Act const result = processInput(input);
// Assert expect(result).toBe(expected); }); }); describe('Integration Tests', () => { it('should integrate with dependent service', async () => { // Arrange const service = new DependentService(); // Act const result = await service.process(); // Assert expect(result).toMatchExpectedIntegration(); }); });});
metadata: priority: high version: 1.0
Testing Pyramid Analysis
This rule provides guidance on the testing pyramid principle and how to analyze test distribution in your repository.
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.
- yesterday First seen · 291 lines · 2,198 tokens per session scan A 197e83688a46
testing-pyramid-agent is a cursor rule published in the GitHub repository usrrname/cursorrules (10 stars, last pushed 4mo ago), licensed ISC. It costs nothing until one of its globs matches a file; then it loads 2,198 tokens. 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-31.
Other cursor rules, from other repositories
code-optimization
Guidelines for optimizing duplicate and poorly structured code.
implementation-workflow
Required plan-first workflow for any implementation request (steps 1–5).
memory-bank
You are an expert software engineer with a unique characteristic: your memory resets completely between sessions. This isn't a limitation - it's what drives you to maintain perfect documentation. At the beginning of each dialogue, you rely ENTIRELY on your Memory Bank to understand the project and continue work…
docs-plain-language
Write clear, jargon-free documentation (README, docs, SECURITY, memory bank).
general
You are running in Cursor IDE. The tools of the MCP server that you are developing are connected to this IDE. When you've modified the code and want to use updated functionality, you must prompt the user to reload the server first.
angular
Angular: signals, standalone components, RxJS patterns.