Borrowing it
Nothing to install: this file belongs to anhtester/claude-testing-kit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/anhtester/claude-testing-kit/main/.claude/commands/generate_combinatorial_test_data.mdgit clone --depth 1 https://github.com/anhtester/claude-testing-kitWrote 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/commands/anhtester/claude-testing-kit/generate_combinatorial_test_data)<a href="https://agentmods.dev/commands/anhtester/claude-testing-kit/generate_combinatorial_test_data"><img src="https://agentmods.dev/badge/commands/anhtester/claude-testing-kit/generate_combinatorial_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/commands/anhtester/claude-testing-kit/generate_combinatorial_test_data"><img src="https://agentmods.dev/badge/commands/anhtester/claude-testing-kit/generate_combinatorial_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.00027 | $0.04167 |
| Opus 5.5 | $0.00011 | $0.01667 |
| Sonnet 5.5 | $0.00005 | $0.00833 |
| Haiku 4.5 | $0.00003 | $0.00417 |
Grade A, and why
generate_combinatorial_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 — 376 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/generate_combinatorial_test_data — Sinh Test Data Cho Ma Trận Kết Hợp
Dùng khi: Đã có ma trận kết hợp (từ
/generate_cross_module_test_plan) và cần tạo test data thực tế bằng cách chạy qua nhiều modules trên browser, hoặc sinh bộ data có cấu trúc sẵn sàng cho automation.
BẮT BUỘC (MANDATORY): Trước khi bắt đầu, PHẢI nạp và đọc kỹ:
- Skill:
.claude/skills/skills-test-data-generator/SKILL.md— Quy tắc sinh data (xem phần Multi-Step Pipeline)- Skill:
.claude/skills/skills-ui-debug-agent/SKILL.md— Inspect DOM khi chạy browser- Workflow:
.claude/commands/generate_cross_module_test_plan.md— Hiểu cấu trúc ma trận đầu vào
Mối quan hệ với các workflows khác
/generate_cross_module_test_plan → Ma trận kết hợp (input)
↓
/generate_combinatorial_test_data → Bộ test data (workflow này)
↓
/generate_manual_testcases_rbt → Test cases chi tiết
↓
/generate_automation_from_testcases → Automation scripts
2 Modes
| Mode | Khi nào dùng | Output |
|---|---|---|
| GENERATE (mặc định) | Sinh bộ data có cấu trúc từ ma trận — KHÔNG chạy browser | File JSON/CSV/Markdown với data cho mỗi bộ kết hợp |
| PIPELINE (lựa chọn cuối) | Bắt buộc phải đi qua UI mới tạo được data | Data thật đã tạo + IDs + screenshots evidence |
Agent tự chọn mode:
- User nói "sinh data", "generate data" → GENERATE
- User nói "tạo data trên hệ thống", "chạy tạo data", "setup data thật" → xem Thứ tự ưu tiên bên dưới
- Nếu không rõ → hỏi user
⚠️ Thứ tự ưu tiên khi cần data THẬT trên hệ thống
PIPELINE (drive browser qua N modules × N combos) là cách đắt nhất và kém ổn định nhất. Trước khi chọn PIPELINE, agent PHẢI hỏi user theo thứ tự:
| # | Cách | Khi nào dùng | Chi phí / Rủi ro |
|---|---|---|---|
| 1 | Seed qua API | Hệ thống có API tạo record | ⭐ Rẻ, nhanh, ổn định — luôn ưu tiên |
| 2 | Seed qua DB / script | Có quyền truy cập DB test | Rẻ, nhanh — cẩn thận ràng buộc toàn vẹn |
| 3 | Import file | Hệ thống hỗ trợ import Excel/CSV | Trung bình |
| 4 | PIPELINE (browser) | 3 cách trên không khả thi — nghiệp vụ chỉ tồn tại ở tầng UI | ⚠️ Chậm, dễ vỡ, để lại rác data |
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 · 376 lines · 27 tokens per session scan A 3fd14204cc20
generate_combinatorial_test_data is a command published in the GitHub repository anhtester/claude-testing-kit (61 stars, last pushed 2mo ago), licensed MIT. It adds 27 tokens to every session and 4,167 once invoked, about $0.0001 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-30.
Other commands, from other repositories
case
A command for registering and managing Testany cases. A case is a reusable package containing one automated testing step, its metadata, and its scripts.
test-reviewer
A review process for an independent test package, checking whether its tests cover the requirements, can be run, and have supporting evidence.
test-spec-writer
A process for turning approved product and technical documents into a complete set of software test cases. It produces a traceability matrix, which links requirements and risks to tests, plus instructions for running and automating them.
test-strategy-reviewer
A command that reviews a software test strategy before detailed design and test specifications begin. It checks the planned tests, environments, dependencies, automation, and release rules.
case-writing
A command that turns traditional test scenarios into Testany platform cases, including metadata, scripts, and uploadable ZIP packages. It supports API, user-interface, end-to-end, Java, and Postman-based tests.
execution
A command for observing and managing Testany executions, meaning individual pipeline runs after they have started. It can show progress and results, search run history, refresh status, and cancel runs that have not started.