What is generate_application_test_plan?

A web-application exploration tool that examines an app's real pages and creates a test plan. A test plan lists important areas, user journeys, scenarios, and their priority.

Use it in PLAN mode for test planning, or FULL mode for a plan plus manual cases and an automation skeleton.

It reduces the risk of planning tests around an imagined application structure. It identifies modules and flows from the supplied application instead.

How anhtester/ClaudeCode_Playwright_Demo configures Claude Code

Reuse

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.

Copy the file

curl -O https://raw.githubusercontent.com/anhtester/ClaudeCode_Playwright_Demo/main/.claude/commands/generate_application_test_plan.md

Clone the repo

git clone --depth 1 https://github.com/anhtester/ClaudeCode_Playwright_Demo

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/anhtester/claudecode_playwright_demo/generate_application_test_plan/github.svg)](https://agentmods.dev/commands/anhtester/claudecode_playwright_demo/generate_application_test_plan)

Your own site

<a href="https://agentmods.dev/commands/anhtester/claudecode_playwright_demo/generate_application_test_plan"><img src="https://agentmods.dev/badge/commands/anhtester/claudecode_playwright_demo/generate_application_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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/anhtester/claudecode_playwright_demo/generate_application_test_plan"><img src="https://agentmods.dev/badge/commands/anhtester/claudecode_playwright_demo/generate_application_test_plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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,514 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 92% copy Near-identical to another mod 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.

Model	Per session	Once invoked
Fable 5.1	$0.00037	$0.01514
Opus 5.5	$0.00015	$0.00606
Sonnet 5.5	$0.00007	$0.00303
Haiku 4.5	$0.00004	$0.00151

Measured 1mo ago against content hash 2e6f1880fbec, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 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.

Origin

This is a copy

92% identical to generate_application_test_plan — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.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 qa_automation_engineer (tại .agent/skills/qa_automation_engineer/SKILL.md) trước khi bắt đầu. Ngoài ra, tham khảo thêm skill requirements_analyzer và 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)

Nhận URL ứng dụng từ user
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
Khám phá navigation menus, sidebar, header để xác định các modules chính
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...)
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.

1mo ago First seen · 116 lines · 37 tokens per session scan A 2e6f1880fbec

Subscribe to this mod's changes

generate_application_test_plan is a command published in the GitHub repository anhtester/ClaudeCode_Playwright_Demo (3 stars, last pushed 5mo ago), licensed MIT. It adds 37 tokens to every session and 1,514 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 92% identical to generate_application_test_plan, differing in 8 lines, and is treated as a copy.

Claude Code E2E testing Testing anhtester automation-framework playwright-typescript

ClaudeCode_Playwright_Demo: Command for Claude Code

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

This is a copy

How it starts

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

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

2 Chế độ (Mode)

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

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

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

What this file has done since we first saw it

Other commands, from other repositories

playwright-test-heal

webapp-testing

verify-pr

test-run

ui-snapshot.template

laravel-playwright