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/oakensoul/nextjs-cursor-prompts/test-create-comprehensivegit clone --depth 1 https://github.com/oakensoul/nextjs-cursor-promptsWrote 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/oakensoul/nextjs-cursor-prompts/test-create-comprehensive)<a href="https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/test-create-comprehensive"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/test-create-comprehensive.svg" alt="Measured on agentmods" 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.00000 | $0.01107 |
| Opus 5 | $0.00000 | $0.00553 |
| Sonnet 5 | $0.00000 | $0.00221 |
| Haiku 4.5 | $0.00000 | $0.00111 |
Grade A, and why
test-create-comprehensive 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 5d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Comprehensive Test Suite
ORCHESTRATION PROMPT: This prompt executes three focused test creation prompts to provide complete test coverage.
FOLLOW MINIMAL CHANGE PRINCIPLES: When creating tests, preserve existing code patterns and architecture. Do not modify working code - only add tests alongside existing functionality.
This prompt will create comprehensive test coverage by executing three specialized test creation prompts in sequence:
- Unit Tests - Core functionality testing for all components, actions, and utilities
- Accessibility Tests - WCAG compliance testing for all UI components
- Integration Tests - End-to-end workflow testing for complex user journeys
Phase 1: Unit Tests
Execute .cursor/prompts/test/test-create-unit.mdc for comprehensive unit test coverage:
- Components, server actions, API routes, utilities, hooks
- Core functionality testing with vitest framework
- Minimum 80% coverage across all metrics
Phase 2: Accessibility Tests
Execute .cursor/prompts/test/test-create-a11y.mdc for WCAG compliance testing:
- All UI components that render to DOM
- WCAG 2.1 AA compliance verification
- Keyboard navigation and screen reader testing
Phase 3: Integration Tests
Execute .cursor/prompts/test/test-create-integration.mdc for end-to-end workflows:
- Complex user journeys and multi-component interactions
- API integration testing with MSW mocking
- State management and cross-component communication
🧪 EXECUTION COMMANDS
Execute these prompts in sequence for complete test coverage:
# Phase 1: Create unit tests
Create comprehensive unit tests following .cursor/prompts/test/test-create-unit.mdc for [target files/directory]
# Phase 2: Create accessibility tests
Create accessibility tests following .cursor/prompts/test/test-create-a11y.mdc for [target UI components]
# Phase 3: Create integration tests
Create integration tests following .cursor/prompts/test/test-create-integration.mdc for [complex workflows]
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.
- 5d ago First seen · 132 lines · 0 tokens per session scan A ddb70a250efd
test-create-comprehensive is a cursor rule published in the GitHub repository oakensoul/nextjs-cursor-prompts (4 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,107 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
use-contract-ir-factories
Use factory functions for creating ContractIR objects instead of manual object creation.
mockito
This guide provides definitive best practices for writing robust, maintainable, and readable unit tests using Mockito with JUnit 5, focusing on modern patterns and common pitfalls.
python-general-coding-standards
应用一般 Python 编码标准，包括类型提示、使用 Pydantic 进行输入验证、后台任务、CORS 处理、安全工具、PEP 8 合规性和全面测试。.
spec-for-ut
Unit testing is essential to ensure the reliability and stability of code, especially for React components and functions. Adhering to best practices and ensuring high test coverage is critical to maintaining a robust codebase.
unit-testing-standards
Cursor rule "unit-testing-standards" from adobecom/da-express-milo, covering unit testing standards, testing philosophy, testing framework stack, test structure patterns and 1. standard test file organization.
project-conventions
Core project conventions for the Uniqlo Sales Alerter.