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-integrationgit 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-integration)<a href="https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/test-create-integration"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/test-create-integration.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.01756 |
| Opus 5 | $0.00000 | $0.00878 |
| Sonnet 5 | $0.00000 | $0.00351 |
| Haiku 4.5 | $0.00000 | $0.00176 |
Grade A, and why
test-create-integration 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 — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Integration Tests
FOCUS: End-to-end workflows, API integrations, and multi-component interactions
EVALUATE NEED: Integration tests are for complex workflows that span multiple components or systems.
Please create integration test coverage for complex user workflows and component interactions, 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
- API Mocking: MSW (Mock Service Worker)
- Mocking: Built-in vitest mocking capabilities
File Structure & Naming (STRICTLY ENFORCED)
- Location: Co-located in
__tests__/subdirectories next to components - Integration Tests:
ComponentName.integration.test.tsx
📋 INTEGRATION TEST REQUIREMENTS
Consider Integration Tests For:
- ✅ Authentication flows
- ✅ Form submissions with validation
- ✅ Multi-step user journeys
- ✅ API data fetching and state updates
- ✅ Component communication
- ✅ Context provider interactions
- ✅ Navigation and routing workflows
- ✅ Complex state management scenarios
Integration Tests Must Include:
- Real API calls (using MSW for mocking)
- End-to-end user workflows
- Cross-component data flow
- State management integration
- Error handling across components
- Loading states and transitions
- User journey completion scenarios
🔧 IMPLEMENTATION STANDARDS
Integration Test Template
import { render, screen, waitFor } from '@testing-library/react'
import userEvent from '@testing-library/user-event'
import { describe, it, expect, beforeEach, afterEach } from 'vitest'
import { server } from '@/test/mocks/server'
import { http, HttpResponse } from 'msw'
import { ComponentName } from './ComponentName'
describe('ComponentName Integration', () => {
beforeEach(() => {
server.listen()
})
afterEach(() => {
server.resetHandlers()
})
it('should complete user workflow end-to-end', async () => {
const user = userEvent.setup()
// Mock API response
server.use(
http.post('/api/submit', () => {
return HttpResponse.json({ success: true })
})
)
render(<ComponentName />)
// Simulate complete user workflow
await user.type(screen.getByLabelText('Email'), '[email protected]')
await user.click(screen.getByRole('button', { name: 'Submit' }))
// Verify end result
await waitFor(() => {
expect(screen.getByText('Success!')).toBeInTheDocument()
})
})
it('should handle API errors gracefully', async () => {
const user = userEvent.setup()
// Mock API error
server.use(
http.post('/api/submit', () => {
return new HttpResponse(null, { status: 500 })
})
)
render(<ComponentName />)
await user.click(screen.getByRole('button', { name: 'Submit' }))
await waitFor(() => {
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 · 261 lines · 0 tokens per session scan A ade24b1aaed2
test-create-integration 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,756 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
maestro-device-selection
Maestro tests can run on either iPhone or iPad simulators based on tags in the test YAML files. This allows you to test iPad-specific UI layouts and features while maintaining a single test suite.
puppeteer
This guide provides opinionated, actionable best practices for writing robust, performant, and maintainable Puppeteer scripts for web scraping, automation, and testing. It emphasizes modern patterns like page.locator() and efficient resource management.
web-pages-e2e-test-maintenance
Keep web pages end-to-end coverage current.
local-compose-db-lifecycle-for-web-tests
Keep local compose DB lifecycle ready for web tests.
xiigen-user-journey-testing
Validate work through a realistic user path. Use for UX, tool workflows, onboarding, and generated instructions.
cypress-e2e-testing-cursorrules-prompt-file
Cursor rules for Cypress development with E2E testing.