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/reliverse/experiments/testing-and-developmentgit clone --depth 1 https://github.com/reliverse/experimentsWhat 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.00855 |
| Opus 5 | $0.00000 | $0.00428 |
| Sonnet 5 | $0.00000 | $0.00171 |
| Haiku 4.5 | $0.00000 | $0.00085 |
Grade A, and why
testing-and-development 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 today.
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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing and Development Workflow
Guidelines for testing and development practices in the Rempts CLI framework.
Testing Framework
- Use Bun's built-in test runner with
bun test - Test files should have
.test.tssuffix intest/directories - Use testing utilities from packages/test/ for CLI-specific testing
Test Structure
// Example test file structure
import { describe, it, expect } from 'bun:test'
import { testCommand } from '@reliverse/rempts-test'
import { myCommand } from '../src/commands/my-command.js'
describe('My Command', () => {
it('should execute successfully', async () => {
const result = await testCommand(myCommand, {
flags: { input: 'test' } // Note: use 'flags', not 'args'
})
expect(result.exitCode).toBe(0)
expect(result.stdout).toContain('success')
})
it('should handle positional arguments', async () => {
const result = await testCommand(myCommand, {
flags: { verbose: true },
args: ['file1.txt', 'file2.txt'] // 'args' is for positional arguments
})
expect(result.stdout).toContain('file1.txt')
})
it('should handle plugin context', async () => {
const result = await testCommand(myCommand, {
flags: { verbose: true },
context: {
store: {
someData: 'test data'
}
}
})
expect(result.stdout).toContain('test data')
})
})
Testing Patterns
- Unit tests: Test individual functions and classes
- Command tests: Use packages/test/src/test-command.ts for CLI testing
- Integration tests: Test complete workflows in packages/test/test/advanced-scenarios.test.ts
Development Commands
From the root directory:
bun dev- Start development mode with watchbun test- Run all testsbun run build- Build all packagesbun run clean- Clean build artifacts
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.
- today First seen · 124 lines · 0 tokens per session scan A c0472798f6e9
testing-and-development is a cursor rule published in the GitHub repository reliverse/experiments (118 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 855 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-09-01.
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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.