test-data-management

test-data-management is a skill for Claude Code from summarybotng/summarybot-ng. It costs 42 tokens per session (1,738 once invoked), scanned A, original, MIT.

A guide to creating, isolating, anonymising, and managing data used by automated tests. It explains synthetic data, which is made-up data, and techniques for avoiding direct use of production personal information.

In plain words
What is it for?
Use it to generate test datasets, protect personal data, prepare performance-test data, or manage cleanup between tests.
Why use it?
It helps tests use realistic and repeatable data without exposing customer information. It also supports edge-case and high-volume testing while addressing privacy requirements.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it to generate test datasets, protect personal data, prepare performance-test data, or manage cleanup between tests.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/summarybotng/summarybot-ng/test-data-management
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.

Any agent
npx skills add summarybotng/summarybot-ng --skill test-data-management
Clone the repo
git clone --depth 1 https://github.com/summarybotng/summarybot-ng

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/summarybotng/summarybot-ng/test-data-management.svg)](https://agentmods.dev/skills/summarybotng/summarybot-ng/test-data-management)
Your own site
<a href="https://agentmods.dev/skills/summarybotng/summarybot-ng/test-data-management"><img src="https://agentmods.dev/badge/skills/summarybotng/summarybot-ng/test-data-management.svg" alt="Measured on agentmods" height="20"></a>
Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,738 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.00042 $0.01738
Opus 5 $0.00021 $0.00869
Sonnet 5 $0.00008 $0.00348
Haiku 4.5 $0.00004 $0.00174

Measured 4d ago against content hash ac21fc400f9a, 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-management 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 4d 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/skills/test-data-management/SKILL.md · 277 lines

How it starts

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

Test Data Management

<default_to_action> When creating or managing test data:

  1. NEVER use production PII directly
  2. GENERATE synthetic data with faker libraries
  3. ANONYMIZE production data if used (mask, hash)
  4. ISOLATE test data (transactions, per-test cleanup)
  5. SCALE with batch generation (10k+ records/sec)

Quick Data Strategy:

  • Unit tests: Minimal data (just enough)
  • Integration: Realistic data (full complexity)
  • Performance: Volume data (10k+ records)

Critical Success Factors:

  • 40% of test failures from inadequate data
  • GDPR fines up to €20M for PII violations
  • Never store production PII in test environments </default_to_action>

Quick Reference Card

When to Use

  • Creating test datasets
  • Handling sensitive data
  • Performance testing with volume
  • GDPR/CCPA compliance

Data Strategies

Type When Size
Minimal Unit tests 1-10 records
Realistic Integration 100-1000 records
Volume Performance 10k+ records
Edge cases Boundary testing Targeted

Privacy Techniques

Technique Use Case
Synthetic Generate fake data (preferred)
Masking j***@example.com
Hashing Irreversible pseudonymization
Tokenization Reversible with key

Synthetic Data Generation

import { faker } from '@faker-js/faker';

// Seed for reproducibility
faker.seed(123);

function generateUser() {
  return {
    id: faker.string.uuid(),
    email: faker.internet.email(),
    firstName: faker.person.firstName(),
    lastName: faker.person.lastName(),
    phone: faker.phone.number(),
    address: {
      street: faker.location.streetAddress(),
      city: faker.location.city(),
      zip: faker.location.zipCode()
    },
    createdAt: faker.date.past()
  };
}

// Generate 1000 users
const users = Array.from({ length: 1000 }, generateUser);

Test Data Builder Pattern

class UserBuilder {
  private user: Partial<User> = {};

  asAdmin() {
    this.user.role = 'admin';
    this.user.permissions = ['read', 'write', 'delete'];
    return this;
  }

  asCustomer() {
    this.user.role = 'customer';
    this.user.permissions = ['read'];
    return this;
  }

  withEmail(email: string) {
    this.user.email = email;
    return this;
  }

  build(): User {
    return {
      id: this.user.id ?? faker.string.uuid(),
      email: this.user.email ?? faker.internet.email(),
      role: this.user.role ?? 'customer',
      ...this.user
    } as User;
  }
}

// Usage
const admin = new UserBuilder().asAdmin().withEmail('[email protected]').build();
const customer = new UserBuilder().asCustomer().build();

Read the full file on GitHub · 277 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 4d ago First seen · 277 lines · 42 tokens per session scan A ac21fc400f9a

Subscribe to this mod's changes

test-data-management is a skill published in the GitHub repository summarybotng/summarybot-ng (2 stars, last pushed 3mo ago), licensed MIT. It adds 42 tokens to every session and 1,738 once invoked, about $0.0002 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.

Related

Other skills, from other repositories

opensearch-agent-right-to-be-forgotten

Fulfil GDPR "right to be forgotten" / erasure and CCPA deletion requests against OpenSearch by finding and removing a person's personal data — including INDIRECT contextual identification, where an individual is identifiable without their name, email, or ID ever appearing (e.g. "the solo frontend engineer on duty…

philterd/opensearch-agent-skill-right-to-be-forgotten · 208 tokens

End-to-End Database Testing

End-to-end database testing with test containers, data seeding, cleanup strategies, transaction isolation, and production data anonymization.

PramodDutta/qaskills · 31 tokens

Faker Test Data Generation

Generating realistic test data with Faker libraries for names, addresses, emails, dates, and domain-specific data with reproducible seed control.

PramodDutta/qaskills · 32 tokens

seed-data

Generate realistic test and seed data for any database schema: users, products, orders, time series, financial data.

JansenAnalytics/claudex · 26 tokens

test-data-generation

Test data generation patterns using Bogus, test builders, and ABP seeders. Use when: (1) creating realistic test data, (2) implementing test data seeders, (3) building test fixtures, (4) generating fake data for development.

thapaliyabikendra/ai-artifacts · 57 tokens

mock-data-generator

A tool that creates realistic sample data from a schema or type definition. Sample data is made-up information used while building or testing software.

chainlesschain/chainlesschain · 19 tokens