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.
git clone --depth 1 https://github.com/katalon-labs/true-skillsWrote 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.
[](https://agentmods.dev/rules/katalon-labs/true-skills/test-data)<a href="https://agentmods.dev/rules/katalon-labs/true-skills/test-data"><img src="https://agentmods.dev/badge/rules/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.
<a href="https://agentmods.dev/rules/katalon-labs/true-skills/test-data"><img src="https://agentmods.dev/badge/rules/katalon-labs/true-skills/test-data.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.5 | $0.00072 | $0.02301 |
| Sonnet 5.5 | $0.00036 | $0.01150 |
| Haiku 4.5 | $0.00018 | $0.00575 |
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 1mo 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.
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
SECRETandVARentries 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, andquery_databasedo 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.
- Manual lane: the case's Pre-condition + per-step Test Data column, written through
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.
- 1mo ago First seen · 348 lines · 179 tokens per session scan A 1379fb3d484a
test-data is a cursor rule published in the GitHub repository katalon-labs/true-skills (10 stars, last pushed 16d ago), licensed MIT. It adds 179 tokens to every session and 5,752 once invoked, about $0.0007 per session on Opus 5.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.
Other cursor rules, from other repositories
tdd-guide
Cursor rule "tdd-guide" from ulises-jeremias/agent-toolkit, covering agent vs skill rule — why agent (cite clause), when to use vs holistic, caller / skills / handoff, the tdd cycle and when invoked.
vibe-test
How to use the vibe-test MCP server for browser testing.
fusebase-flow-validation
Fusebase Flow validation/verification phase rules. Use when running gate checks, reviewing diffs, or verifying smoke prompts.
minimax-m3-status-verification
MiniMax M3 status and verification contract: exact claim labels, proof matching, multimodal-grounded visual claims, and evidence-first closeouts.
testing
Optional Spring Boot example-pack testing rules. Apply only when editing an adopted project or spring-boot profile output.
fusebase-flow-implementation
Fusebase Flow implementation phase rules. Use when editing source code per a locked spec.