generate_application_test_plan

A workflow that explores a web application and produces a test plan in Vietnamese. Test-driven planning means listing important parts of an app, user journeys, and conditions to check; its FULL mode also creates a starting structure for automated tests.

In plain words
What is it for?
Use it to map modules and user flows, write prioritized test scenarios, or generate manual test cases and an automation skeleton when FULL mode is requested.
Why use it?
It bases the plan on the application's actual page structure and requires agreement on the scope before generating detailed cases. This reduces guesses about what the app contains.

Command for Claude Code

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.

agentmods
npx agentmods add commands/anhtester/claude-testing-kit/generate_application_test_plan
Clone the repo
git clone --depth 1 https://github.com/anhtester/claude-testing-kit

Made for: Claude Code.

Per session 37 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,529 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00037 $0.01529
Opus 5 $0.00018 $0.00764
Sonnet 5 $0.00007 $0.00306
Haiku 4.5 $0.00004 $0.00153

Measured 2d ago against content hash d79eee28985a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

generate_application_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 2d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.claude/commands/generate_application_test_plan.md · 116 lines

How it starts

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

Workflow: Khám Phá Ứng Dụng & Sinh Test Plan

BẮT BUỘC (MANDATORY SKILL): Bạn PHẢI nạp và đọc kỹ nội dung của skill skills-qa-automation-engineer (tại .claude/skills/skills-qa-automation-engineer/SKILL.md) trước khi bắt đầu. Ngoài ra, tham khảo thêm skill skills-requirements-analyzerskills-ui-debug-agent để hỗ trợ phân tích UI.

Workflow này giúp agent tự động khám phá một ứng dụng web, phân tích cấu trúc, xác định các modules/user flows quan trọng, và sinh ra Test Plan hoàn chỉnh.

⚠️ Nguyên tắc thực thi

  • Tất cả output bằng Tiếng Việt
  • KHÔNG đoán cấu trúc app — phải inspect DOM thực tế qua MCP/browser tools
  • Phải chờ user xác nhận scope tại Bước 2 trước khi sinh chi tiết
  • Nếu user chưa cung cấp URL → hỏi trước khi bắt đầu

2 Chế độ (Mode)

Mode Khi nào sử dụng Output
PLAN (mặc định) User cần khám phá app, lập test plan, xác định scenarios Modules, User Flows, Test Scenarios, Priority
FULL User yêu cầu thêm automation skeleton hoặc nói "full automation suite" Như PLAN + Manual Test Cases + Automation Skeleton (POM + Test classes)

Nếu user nói "generate full automation suite", "bootstrap automation", hoặc yêu cầu code → tự động chuyển sang Mode FULL.

Các bước thực hiện

Bước 1: Tiếp nhận & Khám phá ứng dụng (Recon)

  1. Nhận URL ứng dụng từ user
  2. Sử dụng MCP browser tools (Playwright MCP) để mở ứng dụng:
    • browser_navigate → URL
    • browser_resize(1920, 1080) → desktop viewport
    • browser_snapshot → thu thập cấu trúc DOM
  3. Khám phá navigation menus, sidebar, header để xác định các modules chính
  4. Lần lượt truy cập từng module chính, dùng browser_snapshot để ghi nhận:
    • Tên module / trang
    • Các thành phần UI chính (forms, tables, buttons, modals)
    • Các action có thể thực hiện (CRUD, search, filter, export...)
  5. Nếu app yêu cầu đăng nhập → hỏi user cung cấp credentials hoặc dùng fixture sẵn có

Bước 2: Phân tích & Xác nhận scope (Analysis — CHECKPOINT)

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

  1. 2d ago First seen · 116 lines · 37 tokens per session scan A d79eee28985a

Subscribe to this mod's changes

generate_application_test_plan is a command published in the GitHub repository anhtester/claude-testing-kit (49 stars, last pushed 24d ago), licensed MIT. It adds 37 tokens to every session and 1,529 once invoked, about $0.0002 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-08-30.