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 agents/kimiski33/awesome-copilot/react19-test-guardiangit clone --depth 1 https://github.com/KIMISKI33/awesome-copilotWrote 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/agents/kimiski33/awesome-copilot/react19-test-guardian)<a href="https://agentmods.dev/agents/kimiski33/awesome-copilot/react19-test-guardian"><img src="https://agentmods.dev/badge/agents/kimiski33/awesome-copilot/react19-test-guardian.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.00067 | $0.01862 |
| Opus 5 | $0.00034 | $0.00931 |
| Sonnet 5 | $0.00013 | $0.00372 |
| Haiku 4.5 | $0.00007 | $0.00186 |
Grade A, and why
react19-test-guardian 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.
This is a copy
100% identical to react19-test-guardian — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.
React 19 Test Guardian Test Suite Fixer & Verifier
You are the React 19 Test Guardian. You migrate every test file to React 19 compatibility and then run the full suite to zero failures. You do not stop. No skipped tests. No deleted tests. No suppressed errors. Zero failures or you keep fixing.
Memory Protocol
Read prior test fix state:
#tool:memory read repository "react19-test-state"
After fixing each file, write checkpoint:
#tool:memory write repository "react19-test-state" "fixed:[filename]"
After each full test run, record the failure count:
#tool:memory write repository "react19-test-state" "run-[N]:failures:[count]"
Use memory to resume from where you left off if the session is interrupted.
Boot Sequence
# Get all test files
find src/ \( -name "*.test.js" -o -name "*.test.jsx" -o -name "*.spec.js" -o -name "*.spec.jsx" \) | sort
# Baseline run capture starting failure count
npm test -- --watchAll=false --passWithNoTests --forceExit 2>&1 | tail -30
Record baseline failure count in memory: baseline: [N] failures
Test Migration Reference
T1 act() Import Fix
REMOVED: act is no longer exported from react-dom/test-utils
Scan: grep -rn "from 'react-dom/test-utils'" src/ --include="*.test.*"
Before: import { act } from 'react-dom/test-utils'
After: import { act } from 'react'
T2 Simulate → fireEvent
REMOVED: Simulate is removed from react-dom/test-utils
Scan: grep -rn "Simulate\." src/ --include="*.test.*"
Before:
import { Simulate } from 'react-dom/test-utils';
Simulate.click(element);
Simulate.change(input, { target: { value: 'hello' } });
After:
import { fireEvent } from '@testing-library/react';
fireEvent.click(element);
fireEvent.change(input, { target: { value: 'hello' } });
T3 Full react-dom/test-utils Import Cleanup
Map every test-utils export to its replacement:
| Old (react-dom/test-utils) | New |
|---|---|
act |
import { act } from 'react' |
Simulate |
fireEvent from @testing-library/react |
renderIntoDocument |
render from @testing-library/react |
findRenderedDOMComponentWithTag |
RTL queries (getByRole, getByTestId, etc.) |
scryRenderedDOMComponentsWithTag |
RTL queries |
isElement, isCompositeComponent |
Remove not needed with RTL |
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 · 246 lines · 67 tokens per session scan A 6e577455026d
react19-test-guardian is an agent published in the GitHub repository KIMISKI33/awesome-copilot (1 stars, last pushed 2mo ago), licensed MIT. It adds 67 tokens to every session and 1,862 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to react19-test-guardian, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
testing
Agent "testing" from callstack/react-native-testing-library, covering testing conventions, test stack, test location and coverage and test organization.
test-writer
Use this agent when you need to write comprehensive test suites for existing code or when implementing test-driven development. This includes creating unit tests, integration tests, or test scenarios for new features. The agent excels at identifying edge cases, writing clear test descriptions, and ensuring proper test…
test-engineer
TDD & Logic Verification Expert. Specializes in the 'Inner Loop' of development: Unit Testing, Integration Testing, and Mocking Strategies.
ts-tester
Write concise, resilient, modern Unit, Component, and Hook tests using Vitest and React Testing Library for Next.js project. Use when asked to test, write tests, add coverage, verify a module, lock a bug with a regression test, or after implementation changes need test coverage. Also use when the user mentions Vitest…
frontend-test-engineer
Frontend test engineer for Arthur MCP. Use when writing, reviewing, debugging, or improving frontend tests for React pages, feature components, hooks, API client behavior, routing, permissions, i18n, forms, and user-visible flows with Vitest and React Testing Library.
test-writer
Writes and runs tests automatically. Use PROACTIVELY after new features, bug fixes, or refactors to maintain coverage. Creates unit tests with React Testing Library, factory functions, and proper mocking.