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/consensys/ask-o11y-plugin/jest-unit-testinggit clone --depth 1 https://github.com/Consensys/ask-o11y-pluginWhat 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.00249 |
| Opus 5 | $0.00000 | $0.00125 |
| Sonnet 5 | $0.00000 | $0.00050 |
| Haiku 4.5 | $0.00000 | $0.00025 |
Grade A, and why
jest-unit-testing 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
Jest Unit Testing
Reference: CLAUDE.md is the authoritative source.
Test Locations
- Unit tests in
src/**/*.test.{ts,tsx}alongside the code they test - Use
data-testidfromsrc/components/testIds.tsfor component references
Focus
Test critical functionality: business logic, utility functions, service classes. Limit to 3–5 focused tests per file.
Best Practices
- Mock dependencies before imports with
jest.mock() - Test three scenarios: valid inputs, invalid inputs, edge cases (null, undefined, unexpected types)
- Descriptive names — test name should describe expected behavior
- Group related tests in
describeblocks - Clear mocks in
beforeEachwithjest.clearAllMocks()
Run Tests
nvm use 22 && npm run test:ci # CI mode
nvm use 22 && npm test -- path/to/test.ts # Single file
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 · 34 lines · 0 tokens per session scan A 71fc56713a91
jest-unit-testing is a cursor rule published in the GitHub repository Consensys/ask-o11y-plugin (40 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 249 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
python_tests
We use the unit tests to cover internal behavior that can work without the web / backend counterpart. We aim for 95%+ unit test coverage of our Python code in lib/streamlit.
unit-tests-tdd
TDD required for behavior changes; ≥80% package coverage on touched packages; unit-test conventions.
commit-checks
Run gofmt, go vet, and unit tests before committing Go files.
unit-testing
Python integration and unit testing — pytest patterns, test classes, workflow test tips.
testing
Testing conventions and Playwright patterns.
unit-testing-standards
Cursor rule "unit-testing-standards" from adobecom/da-express-milo, covering unit testing standards, testing philosophy, testing framework stack, test structure patterns and 1. standard test file organization.