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_cross_module_test_plan.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_cross_module_test_plan)<a href="https://agentmods.dev/commands/anhtester/claude-testing-kit/generate_cross_module_test_plan"><img src="https://agentmods.dev/badge/commands/anhtester/claude-testing-kit/generate_cross_module_test_plan/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_cross_module_test_plan"><img src="https://agentmods.dev/badge/commands/anhtester/claude-testing-kit/generate_cross_module_test_plan.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.00060 | $0.05339 |
| Opus 5.5 | $0.00024 | $0.02136 |
| Sonnet 5.5 | $0.00012 | $0.01068 |
| Haiku 4.5 | $0.00006 | $0.00534 |
Grade A, and why
generate_cross_module_test_plan 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 — 424 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/generate_cross_module_test_plan — Phân Tích Cross-Module & Sinh Ma Trận Kết Hợp
Dùng khi: Tính năng cần test đi qua nhiều modules nối tiếp nhau, mỗi module có nhiều lựa chọn (dimensions), và bộ kết hợp các lựa chọn quyết định output cuối cùng.
BẮT BUỘC (MANDATORY): Trước khi bắt đầu, PHẢI nạp và đọc kỹ:
- Skill:
.claude/skills/skills-qa-automation-engineer/SKILL.md— Workflow routing + automation rules- Skill:
.claude/skills/skills-requirements-analyzer/SKILL.md— Phân tích requirements
Khi nào dùng workflow này?
| Tình huống | Dùng? |
|---|---|
| Tính năng đi qua 1 module/form | ❌ Dùng /generate_manual_testcases_rbt |
| Tính năng đi qua nhiều modules, mỗi module độc lập | ⚠️ Dùng /generate_application_test_plan |
| Tính năng đi qua nhiều modules NỐI TIẾP, output phụ thuộc bộ kết hợp điều kiện | ✅ Đúng workflow này |
| Cần ma trận kết hợp (Output-Class / Pairwise / Decision Table đa chiều) | ✅ Đúng workflow này |
2 Modes
| Mode | Khi nào dùng | Input chính |
|---|---|---|
| DOCUMENT (mặc định) | User cung cấp tài liệu/spec mô tả modules + business rules | File .md, .doc, Jira ticket, hoặc mô tả text |
| BROWSER | User cung cấp URL và muốn agent inspect DOM thực tế | URL ứng dụng + credentials (nếu cần) |
Agent tự chọn mode:
- User cung cấp file/text mô tả → DOCUMENT
- User cung cấp URL hoặc nói "inspect", "mở app", "xem trên browser" → BROWSER
- User cung cấp cả hai → Ưu tiên BROWSER, dùng document để cross-reference
- Nếu không rõ → hỏi user
Input cần từ User
| Input | Bắt buộc | Mô tả |
|---|---|---|
| Tên tính năng / luồng | ✅ | VD: "Biên bản thanh toán cho đối tác" |
| Tài liệu yêu cầu (DOCUMENT mode) | ✅ | File .md, Jira ticket, user story, hoặc text mô tả |
| URL ứng dụng (BROWSER mode) | ✅ | Để agent inspect DOM thực tế |
| Danh sách modules tham gia | ⚠️ Nên có | Nếu không → agent tự extract từ document/browser |
| Danh sách dimensions | ⚠️ Nên có | VD: loại đối tác, loại thuế... Nếu không → agent tự extract |
| Business rules / công thức | ⚠️ Rất nên có | Quyết định Expected Output. Không có → xem Bước 0 |
| Credentials (BROWSER mode) | ❌ | Nếu app cần đăng nhập |
| Chiến lược ma trận | ❌ | output-class (mặc định), pairwise, hoặc full-cartesian |
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 · 424 lines · 60 tokens per session scan A 777d285f67ba
generate_cross_module_test_plan is a command published in the GitHub repository anhtester/claude-testing-kit (61 stars, last pushed 2mo ago), licensed MIT. It adds 60 tokens to every session and 5,339 once invoked, about $0.0002 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.