Borrowing it
Nothing to install: this file belongs to anhtester/ClaudeCode_Playwright_Demo. 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/ClaudeCode_Playwright_Demo/main/.claude/commands/generate_combinatorial_test_data.mdgit clone --depth 1 https://github.com/anhtester/ClaudeCode_Playwright_DemoWrote 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/claudecode_playwright_demo/generate_combinatorial_test_data)<a href="https://agentmods.dev/commands/anhtester/claudecode_playwright_demo/generate_combinatorial_test_data"><img src="https://agentmods.dev/badge/commands/anhtester/claudecode_playwright_demo/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/claudecode_playwright_demo/generate_combinatorial_test_data"><img src="https://agentmods.dev/badge/commands/anhtester/claudecode_playwright_demo/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.03270 |
| Opus 5.5 | $0.00011 | $0.01308 |
| Sonnet 5.5 | $0.00005 | $0.00654 |
| Haiku 4.5 | $0.00003 | $0.00327 |
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 — 323 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:
.agent/skills/test_data_generator/SKILL.md— Quy tắc sinh data (xem phần Multi-Step Pipeline)- Skill:
.agent/skills/ui_debug_agent/SKILL.md— Inspect DOM khi chạy browser- Workflow:
.agent/workflows/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 | Cần tạo data THẬT trên hệ thống bằng cách chạy qua từng module trên browser | 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" → PIPELINE
- Nếu không rõ → hỏi user
Input cần từ User
| Input | Bắt buộc | Mô tả |
|---|---|---|
| Ma trận kết hợp | ✅ | File .md / bảng Markdown từ /generate_cross_module_test_plan |
| URL ứng dụng | ✅ (PIPELINE) | Để agent chạy browser tạo data |
| Credentials | ⚠️ PIPELINE | Nếu app cần đăng nhập |
| Output format | ❌ | json (mặc định), csv, markdown, code (TS/Java/Python) |
| Ngôn ngữ data | ❌ | Tiếng Việt / Tiếng Anh (mặc định: theo context) |
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 · 323 lines · 27 tokens per session scan A f5976222d6a5
generate_combinatorial_test_data is a command published in the GitHub repository anhtester/ClaudeCode_Playwright_Demo (3 stars, last pushed 5mo ago), licensed MIT. It adds 27 tokens to every session and 3,270 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-31.
Other commands, from other repositories
test
Write tests using MCP-powered discovery.
prototype
You are building a proof-of-concept for the current Grainulator sprint. Read CLAUDE.md for sprint context and claims.json for existing research claims.
modernize-transform
Transform one legacy module to the target stack — idiomatic rewrite with behavior-equivalence tests.
test-coverage
Analyze test coverage and identify the highest-value gaps to fill.
flowspec.validate
../../templates/commands/flow/validate.md.
tdd
A command that follows test-driven development (TDD), a method where you write tests before the code they check. It moves through writing a failing test, adding the smallest implementation, and then improving the code.