react-test-writer

react-test-writer is an agent for Claude Code from cicababba/claude-plugins-marketplace. It costs 292 tokens per session (829 once invoked), scanned A, original, MIT.

An agent that writes and maintains tests for React and TypeScript components and application logic.

In plain words
What is it for?
Use it to create unit and integration tests for loading, error, empty, and success states, forms, clicks, keyboard use, focus, responsive behavior, and accessibility attributes.
Why use it?
It helps catch broken user interactions, missing interface states, accessibility problems, and rendering errors as the frontend changes.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter.

Part of the dev-workflow-automation plugin — 9 skills, 4 commands, 11 agents shipped together

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/cicababba/claude-plugins-marketplace/react-test-writer
Clone the repo
git clone --depth 1 https://github.com/cicababba/claude-plugins-marketplace

Made for: Claude Code.

Or install dev-workflow-automation, the plugin that ships this one along with the rest of its 9 skills, 4 commands, 11 agents.

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

agentmods badge for react-test-writer

README.md
[![agentmods](https://agentmods.dev/badge/agents/cicababba/claude-plugins-marketplace/react-test-writer.svg)](https://agentmods.dev/agents/cicababba/claude-plugins-marketplace/react-test-writer)
Your own site
<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="Measured on agentmods" height="20"></a>
Per session 292 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 829 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.1 $0.00292 $0.00829
Opus 5 $0.00146 $0.00415
Sonnet 5 $0.00058 $0.00166
Haiku 4.5 $0.00029 $0.00083

Measured 5d ago against content hash d4ba0b99e9f6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

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 5d 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.

dev-workflow-automation/agents/react-test-writer.md · 58 lines

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.

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. 5d ago First seen · 58 lines · 0 tokens per session scan A d4ba0b99e9f6

Subscribe to this mod's changes

react-test-writer is an agent published in the GitHub repository cicababba/claude-plugins-marketplace (3 stars, last pushed 9mo ago), licensed MIT. It adds 292 tokens to every session and 829 once invoked, about $0.0015 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-08-31.

Related

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.

callstack/react-native-testing-library · 0 tokens

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…

PostHog/posthog · 373 tokens

test-engineer

TDD & Logic Verification Expert. Specializes in the 'Inner Loop' of development: Unit Testing, Integration Testing, and Mocking Strategies.

DDS-Solutions/AI-TadPole-OS · 33 tokens

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…

sergeyklay/.agents · 127 tokens

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.

alexmmatos/arthur-mcp · 59 tokens

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.

Piyush8296/claude-workspace · 44 tokens