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/analyze_flaky_tests.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/analyze_flaky_tests)<a href="https://agentmods.dev/commands/anhtester/claude-testing-kit/analyze_flaky_tests"><img src="https://agentmods.dev/badge/commands/anhtester/claude-testing-kit/analyze_flaky_tests/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/analyze_flaky_tests"><img src="https://agentmods.dev/badge/commands/anhtester/claude-testing-kit/analyze_flaky_tests.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.00052 | $0.03128 |
| Opus 5.5 | $0.00021 | $0.01251 |
| Sonnet 5.5 | $0.00010 | $0.00626 |
| Haiku 4.5 | $0.00005 | $0.00313 |
Grade A, and why
analyze_flaky_tests 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- analyze_flaky_tests — 86% identical, 18 lines differ
How it starts
The opening of the file, as written. The whole thing — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow: Phân Tích & Khắc Phục Flaky Tests
BẮT BUỘC (MANDATORY SKILL): Bạn PHẢI nạp và đọc kỹ nội dung của skill
skills-flaky-test-analyzer(tại.claude/skills/skills-flaky-test-analyzer/SKILL.md) trước khi bắt đầu. Ngoài ra, tham khảo thêm skillskills-smart-locator-agentvàskills-locator-healer-agentkhi cần sửa/thay locator.
Workflow này giúp agent tự động phân tích các automation test không ổn định (lúc pass lúc fail), xác định root cause chính xác, và (tùy mode) tự động sửa code để stabilize test.
⚠️ Nguyên tắc thực thi
- Tất cả output bằng Tiếng Việt
- KHÔNG đoán nguyên nhân — phải phân tích log, code, và DOM thực tế
- Phải chờ user xác nhận danh sách fix tại Bước 3 trước khi sửa code (Mode FIX)
- Nếu user chưa cung cấp test file/error log → hỏi trước khi bắt đầu
- ⚠️ Sau khi user xác nhận fix → agent tự sửa + verify, KHÔNG hỏi lại trong quá trình fix
2 Chế độ (Mode)
| Mode | Khi nào sử dụng | Output |
|---|---|---|
| ANALYZE (mặc định) | User cần hiểu nguyên nhân flaky, chưa muốn sửa code | Báo cáo phân tích + Đề xuất fix |
| FIX | User muốn agent tự sửa code luôn | Như ANALYZE + Code đã sửa + Kết quả verify |
Nếu user nói "sửa luôn", "fix giùm", "khắc phục test này", hoặc yêu cầu agent sửa code → tự động chuyển sang Mode FIX.
Input cần thu thập
Agent cần ít nhất 1 trong các input sau từ user:
| Input | Cách lấy | Độ ưu tiên |
|---|---|---|
| Test file path | User cung cấp hoặc agent tìm trong project | ⭐ Bắt buộc |
| Error log / stack trace | User paste hoặc agent chạy test để thu thập | ⭐ Bắt buộc |
| CI/CD log | User cung cấp URL hoặc file log | Tùy chọn |
| Test report (HTML/JSON) | Playwright report, Allure, TestNG report | Tùy chọn |
| Lịch sử fail | Số lần fail / tổng số lần chạy | Tùy chọn |
Các bước thực hiện
Bước 1: Thu thập thông tin & Tái hiện lỗi (Detect & Reproduce)
- Đọc test file bằng
Read:- Xác định framework (Playwright / Selenium / Appium / Pytest / TestNG)
- Ghi nhận cấu trúc: Page Objects, fixtures, helper functions
- Đánh dấu các vùng code nghi ngờ (waits, locators, assertions, setup/teardown)
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 · 244 lines · 52 tokens per session scan A 67f47d7a9052
analyze_flaky_tests is a command published in the GitHub repository anhtester/claude-testing-kit (61 stars, last pushed 2mo ago), licensed MIT. It adds 52 tokens to every session and 3,128 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.