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 skills add usrrname/cursorrules --skill testing-pyramidgit clone --depth 1 https://github.com/usrrname/cursorrulesWrote 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/skills/usrrname/cursorrules/testing-pyramid)<a href="https://agentmods.dev/skills/usrrname/cursorrules/testing-pyramid"><img src="https://agentmods.dev/badge/skills/usrrname/cursorrules/testing-pyramid/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/skills/usrrname/cursorrules/testing-pyramid"><img src="https://agentmods.dev/badge/skills/usrrname/cursorrules/testing-pyramid.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.00011 | $0.02284 |
| Opus 5.5 | $0.00004 | $0.00914 |
| Sonnet 5.5 | $0.00002 | $0.00457 |
| Haiku 4.5 | $0.00001 | $0.00228 |
Grade A, and why
testing-pyramid 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.
How it starts
The opening of the file, as written. The whole thing — 327 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Distribution Analysis Command 🧪
This command guides the AI agent to analyze test distribution across unit, integration, and E2E tests, and provide recommendations for increasing test coverage and improving test distribution in line with business and technical strategy.
Critical Rules
- Start by identifying the test framework and available coverage tools
- Analyze test distribution using framework-specific commands to list all test files
- Classify tests accurately as unit, integration, or E2E based on multiple indicators
- Target distribution: 70% unit tests, 20% integration tests, 10% E2E tests (this is a guideline at early stages of a project, not a strict requirement)
- Provide actionable recommendations when distribution deviates from ideal ratios
- Consider test file organization, naming conventions, and co-location with source code
- Evaluate test quality indicators (arrange-act-assert pattern, independence, clarity)
- Identify common violations and suggest improvements
Workflow Phases
1. Framework Identification
- Check
package.jsonfor test framework dependencies:- Jest:
jestor@jest/corein dependencies/devDependencies - Vitest:
vitestin dependencies/devDependencies - Playwright:
@playwright/testin dependencies/devDependencies - Cypress:
cypressin dependencies/devDependencies - Mocha:
mochain dependencies/devDependencies
- Jest:
- Identify coverage tools and scripts in
package.json:- Look for
test:coverage,coverage, or scripts with--coverageflags - Note available coverage reporters and formats
- Look for
2. Test Discovery
Use framework-specific commands to list all test files:
- Jest:
npx jest --listTests(lists all test files without running) - Vitest:
npx vitest list(lists all test files) - Playwright:
npx playwright test --list(lists all test specs) - Cypress: Check
cypress.config.jsforspecPatternor runnpx cypress run --dry-run
Checkpoint: Verify all test files are discovered and no test directories are missed.
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 · 327 lines · 11 tokens per session scan A fa655e47669c
testing-pyramid is a skill published in the GitHub repository usrrname/cursorrules (11 stars, last pushed 6mo ago), licensed ISC. It adds 11 tokens to every session and 2,284 once invoked, about $0.0000 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-31.
Other skills, from other repositories
testing
Use when writing or reviewing Flutter/Dart tests (unit, widget, golden), fixing flaky tests, adding coverage, or choosing between unit and widget tests.
test-runner
For a code change, pick the right test tier by change surface, run apc test with baseline diff, and report only NEW reds vs baseline back to the task's acceptance criterion. Separates envblocked from SUT red so a broken machine never fails the code.
designing-tests
Designs and implements testing strategies for any codebase. Use when adding tests, improving coverage, setting up testing infrastructure, debugging test failures, or when asked about unit tests, integration tests, or E2E testing.
backend/testing-guide
A guide for writing backend tests: small unit tests, tests that check connected parts such as an API and database, and end-to-end tests that follow a complete user flow.
patrol-e2e-testing
Use when writing E2E/integration tests, testing native interactions like permissions or system dialogs, capturing UI regressions, or validating cross-platform behavior (Patrol 4.x).
qa/test-strategy
A testing strategy based on the testing pyramid: many small unit tests, fewer integration tests, and a smaller set of end-to-end tests that follow real user journeys. It also defines checks for security, boundaries, permissions, and business consistency.