A test-data planning and setup aid for Katalon, a platform for managing and running software tests. It defines the values and records a test needs before it starts and the cleanup needed afterward.

Use it to identify required data, record preconditions and per-step values, prepare automation fixtures, and plan teardown after a run.

It keeps test data out of scattered step text and makes the same data rules usable for both manual cases and automated tests. This reduces failures caused by missing, stale, or leftover records.

test-data — Command for GitHub Copilot by katalon-labs

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.

Clone the repo

git clone --depth 1 https://github.com/katalon-labs/true-skills

Made for: GitHub Copilot.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/katalon-labs/true-skills/test-data/github.svg)](https://agentmods.dev/commands/katalon-labs/true-skills/test-data)

Your own site

<a href="https://agentmods.dev/commands/katalon-labs/true-skills/test-data"><img src="https://agentmods.dev/badge/commands/katalon-labs/true-skills/test-data/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/katalon-labs/true-skills/test-data"><img src="https://agentmods.dev/badge/commands/katalon-labs/true-skills/test-data.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 179 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 5,752 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.

Model	Per session	Once invoked
Fable 5.1	$0.00179	$0.05752
Opus 5	$0.00089	$0.02876
Sonnet 5	$0.00036	$0.01150
Haiku 4.5	$0.00018	$0.00575

Measured yesterday against content hash 15b57bf16259, 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 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 yesterday.

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.

.github/prompts/test-data.prompt.md · 348 lines

How it starts

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

Katalon Test Data

Use this skill for the data half of test design: which values a case runs on, which records must already exist when it starts, and what has to be true again when it finishes. The steps belong to create-test-cases; the code belongs to test-case-to-playwright; the values, the state, and the cleanup belong here.

One artifact serves both lanes. Call it the data contract: what must exist, which values, and who resets it. A manual case carries the contract in its Pre-condition and per-step Test Data column. An automated suite carries the same contract in a fixture plus a teardown. Design it once, write it down twice.

Availability Boundary

State this before promising anything, because three different things in the Katalon world are called "test data" and the MCP reaches only one of them.

Available via MCP: resolve scope (list_projects, list_repositories); read the requirement the data must satisfy (find_requirements, read_requirement); find the cases the data belongs to (find_test_cases, find_test_cases_by_requirement, read_test_case); write the Pre-condition and the per-step Test Data column into a case (create_test_case, update_test_case); read the target environment (read_auts); group data-dependent cases so they run together (manage_test_folder, find_test_suites, read_test_suite, manage_test_suite).
Not available via MCP, at all:
- No test-data entity, data file, or data binding. The standalone Test Data object (CSV, Excel, internal, database) is a Katalon Studio desktop artifact. The MCP does not create, read, or bind it.
- No secrets or variables. Project SECRET and VAR entries live in the platform UI under Settings -> Configurations -> Secrets & Variables, are referenced in steps as {KEY}, apply to cloud-hosted execution only, and are scoped to the project. There is no tool to read or write them.
- No seeding, no teardown, no database access, no API-call tool. Nothing in the MCP can create or destroy application state.
- No requirement creation. Requirements sync from Jira or Azure; create them there, then find and link.
Do not invent tools. manage_test_data, create_test_data, read_secrets, seed_data, reset_environment, and query_database do not exist. If a workflow seems to need one, use the workaround below and say the boundary out loud.
Run with AI reads the case body and nothing else. Data that is not in the Pre-condition or the Test Data column does not reach the AI runner. This is why the placement rule below is not a style preference.
Workaround, the MCP-legal data contract:
- Manual lane: the case's Pre-condition + per-step Test Data column, written through update_test_case, is the data contract of record.
- Automation lane: a checked-in fixture or factory, plus the seed command named in the case Pre-condition so the manual and coded lanes agree on the same starting state.
- Either way the contract is versioned, reviewable, and needs no tool that does not exist.

Read the full file on GitHub · 348 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.

yesterday First seen · 348 lines · 179 tokens per session scan A 15b57bf16259

Subscribe to this mod's changes

test-data is a command published in the GitHub repository katalon-labs/true-skills (8 stars, last pushed 2d ago), licensed MIT. It adds 179 tokens to every session and 5,752 once invoked, about $0.0009 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-08.

Testing agent-skills agentic-ai ai-testing cursor github-copilot

test-data

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Katalon Test Data

Availability Boundary

What this file has done since we first saw it

Other commands, from other repositories

implement

test-review

run_tests

write-unit-tests

test

implement_tests