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/omril321/automated-notebooklm/testing-practicesgit clone --depth 1 https://github.com/omril321/automated-notebooklmWhat 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.00474 |
| Opus 5 | $0.00000 | $0.00237 |
| Sonnet 5 | $0.00000 | $0.00095 |
| Haiku 4.5 | $0.00000 | $0.00047 |
Grade A, and why
testing-practices 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.
What it actually says
Testing Best Practices
Test File Location
- Place test files next to the files they test, not in separate test directories
- Use naming conventions:
filename.test.tsorfilename.spec.ts - For complex modules, you can use
__tests__/subdirectories within the same folder
What to Test
- Public API: Test the external interface of your modules
- Exported functions: Only test functions that are actually used elsewhere
- Behavior: Focus on what the code does, not how it does it
- Integration points: Test how modules work together
What NOT to Test
- Internal implementation details: Don't test private/internal functions
- Unused functions: If a function isn't exported or used anywhere else, it shouldn't exist
- Implementation specifics: Don't test internal variables, private methods, or implementation details that could change without affecting the public API
Guidelines
- Remove or refactor unused functions instead of testing them
- Keep tests focused on the public contract
- If you need to test internal details, consider if they should be exposed or if the module design needs refactoring
- Test behavior and outcomes, not implementation steps
Running the tests
When running the tests for a single time without watching for changes, use the following command:
yarn test:run
Example Structure
src/
services/
audio-stitcher/
index.ts
index.test.ts ✅ Test next to implementation
utils.ts
utils.test.ts ✅ Test next to implementation
gemini.ts
gemini.test.ts ✅ Test next to implementation
References
- Current project structure shows good examples in src/services/audio-stitcher/ and src/services/google-tts/
- Test setup configuration in tests/setup.ts
- Vitest configuration in vitest.config.ts
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 · 61 lines · 474 tokens per session scan A b1407e5cba2c
testing-practices is a cursor rule published in the GitHub repository omril321/automated-notebooklm (15 stars, last pushed 6mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 474 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-30.
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.