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 skills add fusengine/codex --skill react-testinggit clone --depth 1 https://github.com/fusengine/codexWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/fusengine/codex/react-testing)<a href="https://agentmods.dev/skills/fusengine/codex/react-testing"><img src="https://agentmods.dev/badge/skills/fusengine/codex/react-testing.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00034 | $0.01197 |
| Opus 5 | $0.00017 | $0.00598 |
| Sonnet 5 | $0.00007 | $0.00239 |
| Haiku 4.5 | $0.00003 | $0.00120 |
Grade A, and why
react-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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What ships with it
19 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/accessibility-testing.md 1.6 KB
- references/async-testing.md 1.4 KB
- references/hooks-testing.md 1.4 KB
- references/installation.md 1.5 KB
- references/mocking-patterns.md 1.6 KB
- references/msw-setup.md 1.6 KB
- references/queries.md 1.5 KB
- references/react-19-hooks.md 1.7 KB
- references/templates/accessibility-audit.md 4.4 KB
- references/templates/api-integration.md 4.2 KB
- references/templates/basic-setup.md 2.6 KB
- references/templates/component-async.md 3.5 KB
- references/templates/component-basic.md 3.3 KB
- references/templates/error-boundary.md 3.6 KB
- references/templates/form-testing.md 4.1 KB
- references/templates/hook-basic.md 3.8 KB
- references/templates/suspense-testing.md 3.7 KB
- references/user-events.md 1.4 KB
- references/vitest-config.md 1.3 KB
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 · 167 lines · 34 tokens per session scan A 73bf944bb6da
react-testing is a skill published in the GitHub repository fusengine/codex (1 stars, last pushed 2d ago), with no licence file. It adds 34 tokens to every session and 1,197 once invoked, about $0.0002 per session on Opus 5. 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-03.
Other skills, from other repositories
sfnext-testing
Write tests for Storefront Next using Vitest unit tests, Storybook stories, interaction tests, snapshot tests, and accessibility tests. Use when writing component tests, creating Storybook stories, running test coverage, or setting up test utilities. Covers testing-library patterns, play functions, and coverage…
react-test-engineer
Expert guidance for testing React applications using React Testing Library and Vitest. Focuses on user-centric testing, accessibility, and best practices for unit and integration tests to ensure robust and maintainable code.
testing-react
Use when writing or modifying tests for React hooks.
run-affected-test-file-in-isolation-and-in-co-run-with-its-test-
When delegating a task affected by this skill, include.
use-internals-di-seam-pattern-for-test-injectable-functions
When delegating a task affected by this skill, include.
merge-queue-readiness
Pre-queue merge-group CI simulation. Triggered before adding a PR to a GitHub merge queue. Prevents merge-queue kick-outs from integration test failures.