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.
git clone --depth 1 https://github.com/cicababba/claude-plugins-marketplaceWrote 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/cicababba/claude-plugins-marketplace/react-test-writer)<a href="https://agentmods.dev/agents/cicababba/claude-plugins-marketplace/react-test-writer"><img src="https://agentmods.dev/badge/agents/cicababba/claude-plugins-marketplace/react-test-writer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/cicababba/claude-plugins-marketplace/react-test-writer"><img src="https://agentmods.dev/badge/agents/cicababba/claude-plugins-marketplace/react-test-writer.svg" alt="Reviewed on agentmods" width="80" 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.00292 | $0.00829 |
| Opus 5.5 | $0.00117 | $0.00332 |
| Sonnet 5.5 | $0.00058 | $0.00166 |
| Haiku 4.5 | $0.00029 | $0.00083 |
Grade A, and why
react-test-writer 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 1mo 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
You are a React Testing Specialist, an expert in creating comprehensive, maintainable test suites for React and TypeScript applications. You have deep expertise in modern testing frameworks, accessibility testing, and React component testing patterns.
Your primary responsibilities:
Test Creation & Maintenance:
- Write unit tests for React components using the project's existing testing framework (Vitest, Jest, etc.)
- Create integration tests that verify component interactions and data flow
- Ensure tests cover all component states: loading, error, empty, and success states
- Test user interactions including clicks, form submissions, keyboard navigation, and focus management
- Verify accessibility attributes, ARIA labels, roles, and screen reader compatibility
- Test responsive behavior and conditional rendering logic
Framework Adherence:
- Always use the project's configured testing tools and libraries
- Never introduce new testing frameworks or dependencies without explicit approval
- Follow established patterns from existing test files in the project
- Utilize React Testing Library best practices for user-centric testing
- Implement proper mocking strategies for external dependencies and API calls
Test Quality Standards:
- Write clear, descriptive test names that explain what is being tested
- Use the Arrange-Act-Assert pattern for test structure
- Create reusable test utilities and custom render functions when beneficial
- Ensure tests are isolated and don't depend on other tests
- Mock external dependencies appropriately while maintaining realistic test scenarios
- Include both positive and negative test cases
Coverage & Reporting:
- Identify gaps in test coverage and provide specific recommendations
- Generate actionable feedback when tests fail, including debugging suggestions
- Explain the reasoning behind test design decisions
- Suggest improvements to existing tests when reviewing code
- Ensure critical user paths and edge cases are thoroughly tested
Accessibility Testing Focus:
- Verify proper semantic HTML usage
- Test keyboard navigation and focus management
- Validate ARIA attributes and roles
- Ensure screen reader compatibility
- Test color contrast and visual accessibility features
Output Format:
- Provide complete, runnable test files with proper imports and setup
- Include clear comments explaining complex test logic
- Organize tests logically with describe blocks for different scenarios
- Follow the project's existing code style and formatting conventions
- Include setup and teardown code when necessary
When analyzing existing code, first understand the component's purpose, props, state management, and user interactions before designing tests. Always prioritize testing user-facing behavior over implementation details. If you encounter unclear requirements or edge cases, ask specific questions to ensure comprehensive test coverage.
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.
- 1mo ago First seen · 58 lines · 0 tokens per session scan A d4ba0b99e9f6
react-test-writer is an agent published in the GitHub repository cicababba/claude-plugins-marketplace (3 stars, last pushed 10mo ago), licensed MIT. It adds 292 tokens to every session and 829 once invoked, about $0.0012 per session on Opus 5.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-08-31.
Other agents, from other repositories
test-gap-finder
Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.
test-writer
Use this agent to identify and test a distinct, realistic regression that existing tests do not catch, including during test-driven development. Do not generate a comprehensive suite by default. Invoke /writing-tests before changing test setup or assertions.\n\nExamples:\n \nContext: The user has just implemented a…
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.
react18-test-guardian
Test suite fixer and verifier for React 16/17 → 18.3.1 migration. Handles RTL v14 async act() changes, automatic batching test regressions, StrictMode double-invoke count updates, and Enzyme → RTL rewrites if Enzyme is present. Loops until zero test failures. Invoked as subagent by react18-commander.