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-unitgit 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-unit)<a href="https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/test-create-unit"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/test-create-unit.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 | $0.00000 | $0.01167 |
| Opus 5 | $0.00000 | $0.00583 |
| Sonnet 5 | $0.00000 | $0.00233 |
| Haiku 4.5 | $0.00000 | $0.00117 |
Grade A, and why
test-create-unit 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 4d 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Unit Tests
FOCUS: Unit tests for components, server actions, API routes, utilities, and hooks
FOLLOW MINIMAL CHANGE PRINCIPLES: When creating tests, preserve existing code patterns and architecture. Do not modify working code - only add tests alongside existing functionality.
Please create comprehensive unit test coverage for the code I'm working on, following our vitest-based testing standards.
🧪 MANDATORY TESTING FRAMEWORK REQUIREMENTS
Testing Stack (NO EXCEPTIONS)
- Primary Framework: vitest (NEVER Jest)
- DOM Environment: happy-dom
- Component Testing: @testing-library/react
- User Interactions: @testing-library/user-event
- Mocking: Built-in vitest mocking capabilities
File Structure & Naming (STRICTLY ENFORCED)
- Location: Co-located in
__tests__/subdirectories next to components - Unit Tests:
ComponentName.test.tsxorfunction-name.test.ts
📋 UNIT TEST REQUIREMENTS
Components Must Test:
- Basic rendering with default props
- All prop variations and combinations
- User interactions (clicks, form input, etc.)
- Error states and error boundaries
- Loading states (if applicable)
- Conditional rendering logic
- Event handlers and callbacks
Server Actions Must Test:
- Success cases with valid input
- Error handling and validation
- Input sanitization and validation
- Return value structure and types
- Side effects (database operations, etc.)
API Routes Must Test:
- All HTTP methods (GET, POST, PUT, DELETE)
- Request/response handling
- Authentication and authorization
- Input validation and sanitization
- Error responses and status codes
Utilities/Hooks Must Test:
- Core functionality and behavior
- Edge cases and boundary conditions
- Error conditions and handling
- All function parameters and return types
🔧 IMPLEMENTATION STANDARDS
Unit Test Template
import { render, screen } from '@testing-library/react'
import userEvent from '@testing-library/user-event'
import { describe, it, expect, vi } from 'vitest'
import { ComponentName } from './ComponentName'
describe('ComponentName', () => {
it('should render correctly', () => {
render(<ComponentName />)
expect(screen.getByRole('button')).toBeInTheDocument()
})
it('should handle user interactions', async () => {
const user = userEvent.setup()
const mockHandler = vi.fn()
render(<ComponentName onClick={mockHandler} />)
await user.click(screen.getByRole('button'))
expect(mockHandler).toHaveBeenCalledOnce()
})
it('should handle error states', () => {
render(<ComponentName error="Something went wrong" />)
expect(screen.getByText('Something went wrong')).toBeInTheDocument()
})
})
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.
- 4d ago First seen · 153 lines · 0 tokens per session scan A 3f85fae52492
test-create-unit 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,167 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
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.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.