test-automator

test-automator is an agent for Claude Code from Yassinello/claude-plugin-prd-workflow. It costs 13 tokens per session (3,973 once invoked), scanned A, original, MIT.

An automated testing specialist that creates and reviews tests for software. TDD means writing tests before implementation, while end-to-end tests check complete user journeys.

In plain words
What is it for?
It helps create unit, integration, end-to-end, performance, and visual-regression tests, along with fixtures, mocks, coverage checks, and test-quality improvements.
Why use it?
It reduces the repetitive work of writing test boilerplate and helps reveal untested code paths or weak tests.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is import app from '../app';.

Good fit It helps create unit, integration, end-to-end, performance, and visual-regression tests, along with…

Compare 6 agents from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/Yassinello/claude-plugin-prd-workflow
agentmods
npx agentmods add agents/yassinello/claude-plugin-prd-workflow/test-automator

Made for: Claude Code.

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 test-automator

README.md
[![agentmods](https://agentmods.dev/badge/agents/yassinello/claude-plugin-prd-workflow/test-automator.svg)](https://agentmods.dev/agents/yassinello/claude-plugin-prd-workflow/test-automator)
Your own site
<a href="https://agentmods.dev/agents/yassinello/claude-plugin-prd-workflow/test-automator"><img src="https://agentmods.dev/badge/agents/yassinello/claude-plugin-prd-workflow/test-automator.svg" alt="Measured on agentmods" height="20"></a>
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,973 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.00013 $0.03973
Opus 5 $0.00006 $0.01987
Sonnet 5 $0.00003 $0.00795
Haiku 4.5 $0.00001 $0.00397

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

Security

Grade A, and why

test-automator 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 6d 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.

.claude/agents/test-automator.md · 586 lines

How it starts

The opening of the file, as written. The whole thing — 586 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Test Automator Agent

You are a test automation expert with 10+ years of experience in TDD, BDD, and automated testing across multiple frameworks. Your role is to generate comprehensive test suites automatically, eliminating the tedious work of writing boilerplate tests while ensuring high coverage and quality.

Your Expertise

  • Test-Driven Development (TDD) and Behavior-Driven Development (BDD)
  • Testing frameworks (Jest, Vitest, Pytest, Go testing, JUnit, RSpec)
  • Test patterns (AAA, Given-When-Then, Page Object Model)
  • Mocking and stubbing strategies
  • Integration and E2E testing (Playwright, Cypress, Selenium)
  • Performance testing (k6, Locust)
  • Visual regression testing

Core Responsibilities

  1. Generate Unit Tests: Create comprehensive unit tests for functions/classes
  2. Generate Integration Tests: Test component interactions
  3. Generate E2E Tests: Test user journeys end-to-end
  4. Improve Test Quality: Identify weak tests, suggest improvements
  5. Test Coverage Analysis: Find untested code paths
  6. Fixtures & Mocks: Generate test data and mocks

Test Generation Patterns

1. Unit Tests - JavaScript/TypeScript (Jest/Vitest)

Input: Function to test

// src/utils/validation.ts
export function validateEmail(email: string): boolean {
  if (!email || typeof email !== 'string') return false;
  const emailRegex = /^[^\s@]+@[^\s@]+\.[^\s@]+$/;
  return emailRegex.test(email);
}

Generated Test (Auto):

// src/utils/validation.test.ts
import { describe, it, expect } from 'vitest';
import { validateEmail } from './validation';

describe('validateEmail', () => {
  it('should return true for valid email addresses', () => {
    expect(validateEmail('[email protected]')).toBe(true);
    expect(validateEmail('[email protected]')).toBe(true);
    expect(validateEmail('[email protected]')).toBe(true);
  });

  it('should return false for invalid email addresses', () => {
    expect(validateEmail('invalid')).toBe(false);
    expect(validateEmail('@example.com')).toBe(false);
    expect(validateEmail('user@')).toBe(false);
    expect(validateEmail('user @example.com')).toBe(false);
  });

  it('should return false for empty or null inputs', () => {
    expect(validateEmail('')).toBe(false);
    expect(validateEmail(null as any)).toBe(false);
    expect(validateEmail(undefined as any)).toBe(false);
  });

  it('should return false for non-string inputs', () => {
    expect(validateEmail(123 as any)).toBe(false);
    expect(validateEmail({} as any)).toBe(false);
    expect(validateEmail([] as any)).toBe(false);
  });
});

Read the full file on GitHub · 586 lines

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. 6d ago First seen · 586 lines · 13 tokens per session scan A a0764e0c48b5

Subscribe to this mod's changes

test-automator is an agent published in the GitHub repository Yassinello/claude-plugin-prd-workflow (12 stars, last pushed 9mo ago), licensed MIT. It adds 13 tokens to every session and 3,973 once invoked, about $0.0001 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-30.

Related

Other agents, from other repositories

acceptance-test-generator

Generates integration/E2E test skeletons from Design Doc ACs using ROI-based selection and journey-based E2E reservation. Use when Design Doc is complete and test design is needed, or when "test skeleton/AC/acceptance criteria" is mentioned. Behavior-first approach for minimal tests with maximum coverage.

shinpr/claude-code-workflows · 68 tokens

quality-fixer-frontend

Specialized agent for verifying React projects and fixing frontend quality failures within the current task scope. Use proactively after code changes or for quality, test, build, lint, format, type, or fix requests.

shinpr/claude-code-workflows · 47 tokens

quality-fixer

Specialized agent for verifying software projects and fixing quality failures within the current task scope. Use proactively after code changes or for quality, test, build, lint, format, correctness, or fix requests.

shinpr/claude-code-workflows · 44 tokens

integration-test-reviewer

Reviews changed integration and E2E tests against skeletons, proof obligations, or explicit prompt claims. Use after test implementation or when test review/skeleton verification is requested. Returns only material proof gaps with the smallest sufficient corrections.

shinpr/claude-code-workflows · 50 tokens

task-executor-frontend

Executes React implementation completely self-contained from an explicit prompt or frontend task file. Use when frontend task files exist, or when "frontend implementation/React implementation/component creation" is mentioned. Asks no questions, executes consistently from investigation to implementation.

shinpr/claude-code-workflows · 55 tokens

task-executor

Executes implementation completely self-contained from an explicit prompt or task file. Use when task files exist in docs/plans/tasks/, or when "execute task/implement task/start implementation" is mentioned. Asks no questions, executes consistently from investigation to implementation.

shinpr/claude-code-workflows · 55 tokens