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/madebyaris/rakitui-ai/testing-strategygit clone --depth 1 https://github.com/madebyaris/rakitui-aiWhat 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.00384 |
| Opus 5 | $0.00000 | $0.00192 |
| Sonnet 5 | $0.00000 | $0.00077 |
| Haiku 4.5 | $0.00000 | $0.00038 |
Grade A, and why
testing-strategy 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 3d 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.
What it actually says
Testing Strategy
Comprehensive testing approach for the Rakit UI AI design selection tool.
Test Structure
tests/
├── unit/
│ ├── DesignselectionTool.test.ts
│ ├── serverUtils.test.ts
│ └── designSelection.test.ts
├── integration/
│ └── selection-flow.test.ts
└── e2e/
└── browser-selection.test.ts
Unit Testing
Test individual functions in isolation:
DesignselectionTool Tests
- Test schema validation
- Test execute method with various inputs
- Test error handling
- Mock dependencies (serverUtils)
ServerUtils Tests
- Test server creation and port handling
- Test state management functions
- Test cleanup mechanisms
- Mock HTTP server and file system
Template Tests
- Test HTML generation with different inputs
- Test XSS prevention
- Test template escaping
Integration Testing
Test component interactions:
- Server startup and shutdown flow
- Selection process end-to-end
- Error recovery mechanisms
- Timeout handling
E2E Testing
Test full user flows using Playwright:
- Browser opens correctly
- Design options display properly
- Selection process works
- Browser closes after selection
- Multiple simultaneous sessions
Testing Tools
- Jest: Unit and integration tests
- Playwright: E2E browser tests
- Supertest: HTTP endpoint testing
- Mock Service Worker: API mocking
Coverage Goals
- Unit tests: 80% coverage minimum
- Integration tests: Critical paths covered
- E2E tests: Happy path + key error scenarios
CI/CD Integration
- Run tests on every pull request
- Block merging if tests fail
- Generate coverage reports
- Performance benchmarking
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.
- 3d ago First seen · 81 lines · 0 tokens per session scan A 728ca4ffbbdb
testing-strategy is a cursor rule published in the GitHub repository madebyaris/rakitui-ai (5 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 384 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
300-testing
Comprehensive testing guide covering unit, integration, E2E, test frameworks, patterns, and CI/CD integration.
testing
Testing conventions and Playwright patterns.
testing-guide
Cursor rule "testing-guide" from HeeGyeong/ComposeSample, covering testing guide, unit tests, ui tests, test coverage and performance testing.
050-testing
Reglas de testing — asegurar que el código funciona antes de operar con dinero real.
tester
Tester role - Unit, E2E, and visual regression testing.
002-verify-before-act
Requires Claude to read before writing, verify before installing, and confirm before destructive operations.