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 commands/farzannajipour/cursor-react-rules/add-testsgit clone --depth 1 https://github.com/Farzannajipour/cursor-react-rulesWhat 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.00537 |
| Opus 5 | $0.00000 | $0.00269 |
| Sonnet 5 | $0.00000 | $0.00107 |
| Haiku 4.5 | $0.00000 | $0.00054 |
Grade A, and why
add-tests 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 2d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add Tests
Overview
Add comprehensive tests for React components or functions using React Testing Library and Jest.
Steps
-
Create test file
- Name: ComponentName.test.tsx
- Co-locate with component file
-
Write test structure
- Use describe blocks for organization
- Test rendering, interactions, states
- Test accessibility
-
Mock dependencies
- Mock API calls with jest.fn()
- Mock Next.js router
- Mock external libraries
-
Test user behavior
- Use userEvent for interactions
- Test what users see and do
- Avoid testing implementation details
Template
import { render, screen, waitFor } from '@testing-library/react';
import userEvent from '@testing-library/user-event';
import { ComponentName } from './ComponentName';
describe('ComponentName', () => {
describe('Rendering', () => {
it('renders with required props', () => {
render(<ComponentName prop="value" />);
expect(screen.getByRole('button')).toBeInTheDocument();
});
});
describe('User Interactions', () => {
it('handles click events', async () => {
const user = userEvent.setup();
const handleClick = jest.fn();
render(<ComponentName onClick={handleClick} />);
await user.click(screen.getByRole('button'));
expect(handleClick).toHaveBeenCalledTimes(1);
});
});
describe('States', () => {
it('displays loading state', () => {
render(<ComponentName isLoading />);
expect(screen.getByText(/loading/i)).toBeInTheDocument();
});
it('displays error state', () => {
const error = new Error('Test error');
render(<ComponentName error={error} />);
expect(screen.getByRole('alert')).toHaveTextContent('Test error');
});
});
describe('Accessibility', () => {
it('has proper ARIA attributes', () => {
render(<ComponentName />);
const button = screen.getByRole('button');
expect(button).toHaveAttribute('aria-label');
});
});
});
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.
- 2d ago First seen · 89 lines · 0 tokens per session scan A 5685fe10d89b
add-tests is a command published in the GitHub repository Farzannajipour/cursor-react-rules (3 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 537 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 commands, from other repositories
design-to-code
Mockup-to-component pipeline using Google Stitch, 21st.dev, and Storybook MCP. Accepts a screenshot, a description, or a URL and produces production-ready React components, checking existing Storybook components before generating anything new. Use when implementing UI from a mockup or screenshot. To call the MCP tool…
go-test
Go TDD workflow with table-driven tests.
component
Scaffold a new React component grounded in the paper-mono primitives. Requires explicit kind or a nearest-existing-component match. No empty divs, no speculative scaffolding.
run-all-tests-and-fix
Execute the full test suite and systematically fix any failures, ensuring code quality and functionality. All test-related commands must pass before completion.
test
Run the Kotlin unit test suite (optionally filtered to a class or method).
test
Generate comprehensive tests.