testing

Testing instructions for a React Native testing-library project that uses Jest. They explain the test setup, typical test locations, coverage rules, and how to organize test groups.

In plain words
What is it for?
Use them when adding or changing tests under the source tree. They guide the choice of test environment, file location, grouping, and whether to use test or it.
Why use it?
They make new tests fit the existing test suite and avoid misleading coverage or unnecessarily nested test structures.

Agent

Install

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.

agentmods
npx agentmods add agents/callstack/react-native-testing-library/testing
Clone the repo
git clone --depth 1 https://github.com/callstack/react-native-testing-library
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 147 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What 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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00147
Opus 5 $0.00000 $0.00073
Sonnet 5 $0.00000 $0.00029
Haiku 4.5 $0.00000 $0.00015

Measured yesterday against content hash efb83980b07c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 yesterday.

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.

agents/testing.md · 21 lines

What it actually says

Testing Conventions

Test stack

  • Test framework: Jest with the react-native preset
  • Test environment setup: jest-setup.ts
  • Auto-cleanup is configured from src/index.ts unless explicitly skipped

Test location and coverage

  • Library tests are typically colocated under src/**/__tests__
  • Coverage is collected from src and excludes test files

Test organization

  • Use describe blocks to group tests by theme.
  • Do not put all tests into a single describe.
  • Avoid nested describe blocks.
  • If a describe would contain only one test, make that test top-level instead.
  • Prefer test over it.
Changes

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.

  1. yesterday First seen · 21 lines · 0 tokens per session scan A efb83980b07c

Subscribe to this mod's changes

testing is an agent published in the GitHub repository callstack/react-native-testing-library (3,414 stars, last pushed 19d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 147 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.