test-data-factory

test-data-factory is a command for Claude Code from sigistry/marketplace. It costs 12 tokens per session (4,342 once invoked), scanned A, original, MIT.

A command that creates realistic test data, fixtures, and mock factories from the models in a codebase. Fixtures and mocks are prepared data and stand-ins used by tests.

In plain words
What is it for?
It is for generating test records for entities such as users, products, and orders across several programming languages.
Why use it?
It reduces the manual work of building consistent test data and helps tests use valid examples that can still be customized.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. 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 { User, UserRole } from '../models/User';.

Part of the test-generator plugin — 5 commands shipped together

Good fit It is for generating test records for entities such as users, products, and orders across several programming languages.

Compare 6 commands 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/sigistry/marketplace
agentmods
npx agentmods add commands/sigistry/marketplace/test-data-factory

Made for: Claude Code.

Or install test-generator, the plugin that ships this one along with the rest of its 5 commands.

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-data-factory

README.md
[![agentmods](https://agentmods.dev/badge/commands/sigistry/marketplace/test-data-factory/github.svg)](https://agentmods.dev/commands/sigistry/marketplace/test-data-factory)
Your own site
<a href="https://agentmods.dev/commands/sigistry/marketplace/test-data-factory"><img src="https://agentmods.dev/badge/commands/sigistry/marketplace/test-data-factory/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.

agentmods 80×15 button for test-data-factory

Your own site · 80×15
<a href="https://agentmods.dev/commands/sigistry/marketplace/test-data-factory"><img src="https://agentmods.dev/badge/commands/sigistry/marketplace/test-data-factory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,342 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.00012 $0.04342
Opus 5 $0.00006 $0.02171
Sonnet 5 $0.00002 $0.00868
Haiku 4.5 $0.00001 $0.00434

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

Security

Grade A, and why

test-data-factory 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.

plugins/test-generator/commands/test-data-factory.md · 752 lines

How it starts

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

Test Data Factory Generation Command

You are tasked with generating comprehensive test data factories that create realistic, consistent test data for your tests. These factories should make it easy to generate valid test instances with sensible defaults while allowing customization.

Step 1: Identify Target Entities

If the user provided entity/model names:

  • Locate the corresponding data models, classes, or type definitions
  • Identify all properties and their types
  • Understand relationships between entities

If no specific entities are provided:

  • Scan the codebase for data models
  • Suggest common entities: User, Product, Order, etc.
  • Show recently modified models

Common entity locations:

  • TypeScript: interfaces, types, models
  • Python: models.py, schemas.py, dataclasses
  • Java: entity classes, DTOs
  • Go: structs

Step 2: Analyze Entity Structure

For each entity, extract:

Basic Properties

  • Property names
  • Data types (string, number, boolean, date, etc.)
  • Required vs optional fields
  • Default values
  • Constraints (min/max, length, format)

Complex Properties

  • Nested objects
  • Arrays and collections
  • Enums and unions
  • Relationships (foreign keys, references)

Validation Rules

  • Format requirements (email, URL, phone)
  • Range constraints (min, max values)
  • Length limits
  • Regular expression patterns
  • Custom validators

Example Analysis:

// Source: User.ts
interface User {
  id: string;              // UUID
  email: string;           // Valid email format
  firstName: string;       // 1-50 chars
  lastName: string;        // 1-50 chars
  age?: number;           // Optional, 18-120
  role: 'admin' | 'user'; // Enum
  createdAt: Date;
  settings: UserSettings; // Nested object
  orders: Order[];        // Array of related entities
}

Step 3: Detect Faker/Mock Library

Identify available data generation libraries:

JavaScript/TypeScript

  • @faker-js/faker (recommended): Comprehensive fake data
  • chance: Random data generator
  • casual: Fake data for testing
  • Install if not present: npm install -D @faker-js/faker

Read the full file on GitHub · 752 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. 5d ago First seen · 752 lines · 12 tokens per session scan A 6631d27ed94e

Subscribe to this mod's changes

test-data-factory is a command published in the GitHub repository sigistry/marketplace (3 stars, last pushed 4d ago), licensed MIT. It adds 12 tokens to every session and 4,342 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-09-03.