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_manual_testcases_rbt.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_manual_testcases_rbt)<a href="https://agentmods.dev/commands/anhtester/claudecode_playwright_demo/generate_manual_testcases_rbt"><img src="https://agentmods.dev/badge/commands/anhtester/claudecode_playwright_demo/generate_manual_testcases_rbt/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_manual_testcases_rbt"><img src="https://agentmods.dev/badge/commands/anhtester/claudecode_playwright_demo/generate_manual_testcases_rbt.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.00024 | $0.01063 |
| Opus 5 | $0.00012 | $0.00531 |
| Sonnet 5 | $0.00005 | $0.00213 |
| Haiku 4.5 | $0.00002 | $0.00106 |
Grade A, and why
generate_manual_testcases_rbt 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 9d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BẮT BUỘC (MANDATORY SKILL): Bạn PHẢI nạp và đọc kỹ nội dung của skill
rbt_manual_testing(tại.agent/skills/rbt_manual_testing/SKILL.md) trước khi bắt đầu thực hiện tác vụ này. Sử dụng Mode FULL RBT của skill. Ngoài ra, tham khảo thêm skillrequirements_analyzerđể hiểu cách phân tích giao diện nếu cần.
Workflow: Sinh Manual Test Cases theo AI-RBT Framework (FULL RBT Mode)
Workflow này sử dụng Mode FULL RBT của skill rbt_manual_testing — quy trình AI-RBT (AI-Driven Risk-Based Testing) gồm 6 bước tuần tự để sinh manual test cases từ tài liệu yêu cầu.
[!NOTE] Luồng này dành cho Antigravity (slash command). Agent thực hiện theo hướng dẫn trong skill, KHÔNG cần đọc file prompt.txt. Nếu QA team muốn dùng prompt chi tiết hơn (ChatGPT/Claude), hãy copy-paste từng bước từ
plans/manual/01-06/prompt.txt.
⚠️ Nguyên tắc thực thi
- Mode: FULL RBT (6 bước tuần tự)
- BẮT BUỘC chạy tuần tự từng bước, KHÔNG gộp nhiều bước
- PHẢI dừng lại chờ user phản hồi tại Bước 2 (Q&A) và Bước 4 (Review Scenarios)
- Nếu user chưa cung cấp requirements, hỏi user cung cấp trước khi bắt đầu
- Tất cả output bằng Tiếng Việt
Các bước thực hiện
Thực hiện theo hướng dẫn chi tiết trong skill rbt_manual_testing → phần Mode 2: FULL RBT.
Bước 1: Khởi tạo ngữ cảnh (Context & Role-play)
- Yêu cầu user cung cấp: tên dự án, mô tả hệ thống, mục tiêu MVP, tài liệu yêu cầu
- Đọc kỹ tài liệu, xác nhận hiểu bối cảnh
- Chờ user xác nhận → sang Bước 2
Bước 2: Phân tích yêu cầu (Analysis & QnA)
- Xác định Happy Path, Alternate Paths, Exception Paths
- Phát hiện Ambiguities (thiếu sót, mâu thuẫn, chưa rõ ràng)
- Đặt câu hỏi Q&A có đánh số (Q1, Q2...) cho user/PO/BA, kèm ngữ cảnh + assumption
- DỪNG LẠI — Chờ user trả lời câu hỏi → sang Bước 3
Bước 3: Phân rã hệ thống (Decomposition)
- Chia tính năng thành Modules / Sub-modules
- Mô tả chức năng từng Module + Dependencies giữa chúng
Bước 4: Đảm bảo độ bao phủ (Traceability)
- Map Module → mã Yêu cầu (REQ-01, REQ-02...)
- Cross-check thiếu sót (Gap Analysis), liệt kê High-Level Scenarios
- Chờ user review scenarios → sang Bước 5
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.
- 9d ago First seen · 74 lines · 24 tokens per session scan A 0cbea873d215
generate_manual_testcases_rbt is a command published in the GitHub repository anhtester/ClaudeCode_Playwright_Demo (2 stars, last pushed 3mo ago), licensed MIT. It adds 24 tokens to every session and 1,063 once invoked, about $0.0001 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-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.
verify
Run repository verification using the verification-loop skill.
test-coverage
Analyze test coverage and identify the highest-value gaps to fill.
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.
check-dev
Type-check a Z specification with fuzz.