What is generate_locator?

A command that creates stable selectors for finding buttons, fields, and other elements in web or mobile interfaces. It supports Playwright, Selenium, and Appium.

Use it to create or review selectors from an element description, URL, screenshot, or HTML snippet. It helps automate websites and mobile apps with Playwright, Selenium, or Appium.

It reduces fragile tests caused by selectors that stop working when a page changes. It checks the real page structure and whether the selector matches only the intended element.

How anhtester/claude-testing-kit configures Claude Code

Reuse

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.

Copy the file

curl -O https://raw.githubusercontent.com/anhtester/claude-testing-kit/main/.claude/commands/generate_locator.md

Clone the repo

git clone --depth 1 https://github.com/anhtester/claude-testing-kit

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/claude-testing-kit/generate_locator/github.svg)](https://agentmods.dev/commands/anhtester/claude-testing-kit/generate_locator)

Your own site

<a href="https://agentmods.dev/commands/anhtester/claude-testing-kit/generate_locator"><img src="https://agentmods.dev/badge/commands/anhtester/claude-testing-kit/generate_locator/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/claude-testing-kit/generate_locator"><img src="https://agentmods.dev/badge/commands/anhtester/claude-testing-kit/generate_locator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 3,012 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 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.

Model	Per session	Once invoked
Fable 5.1	$0.00020	$0.03012
Opus 5.5	$0.00008	$0.01205
Sonnet 5.5	$0.00004	$0.00602
Haiku 4.5	$0.00002	$0.00301

Measured 1mo ago against content hash c7a93d37cf43, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

generate_locator 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

Copies of this mod

1 near-identical copy found in the catalogue:

generate_locator — 98% identical, 18 lines differ

.claude/commands/generate_locator.md · 334 lines

How it starts

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

/generate_locator — Sinh Locator Ổn Định Cho UI Automation

User cung cấp element cần tìm locator (mô tả, screenshot, URL, hoặc HTML snippet). AI inspect DOM/UI hierarchy thực tế, sinh locator ổn định theo priority chuẩn, verify uniqueness, trả về kết quả.

BẮT BUỘC (MANDATORY): Trước khi bắt đầu, PHẢI nạp và đọc kỹ:

Skill: .claude/skills/skills-smart-locator-agent/SKILL.md — Quy trình sinh locator

Skill: .claude/skills/skills-ui-debug-agent/SKILL.md — Quy trình inspect DOM

Rule: .claude/rules/locator_strategy.md — Bản đồ ưu tiên locator

Rule: .claude/rules/<framework>_rules.md — Quy tắc riêng framework đang dùng

Input cần từ User

Input	Bắt buộc	Mô tả
Mô tả element	✅	VD: "nút Login", "dropdown chọn Country", "ô nhập Email"
URL trang chứa element	✅	Để AI navigate và inspect DOM thực tế
Framework	✅	`playwright`, `selenium`, hoặc `appium`
HTML snippet	❌	Nếu User đã có sẵn DOM context — AI dùng để phân tích nhanh
Page class đích	❌	File Page class mà locator sẽ được thêm vào
Login yêu cầu	❌	Nếu trang yêu cầu đăng nhập — User cho biết cách login

Lưu ý về Login: Nếu trang yêu cầu đăng nhập, User PHẢI chỉ rõ cách login (fixture, script, URL login...). AI KHÔNG ĐƯỢC tự đọc .env hay đoán credentials.

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

Phase 1: Phân tích yêu cầu

Hiểu element cần tìm — Xác định rõ:
- Loại element: button, input, link, dropdown, dialog, table row, checkbox, radio...
- Context: Nằm trong page chính, dialog/modal, sidebar, table, iframe?
- Thao tác: click, fill, select, hover, verify text, verify visibility?
Xác định framework và đọc rules tương ứng:

Framework Rule file

Playwright .claude/rules/playwright_rules.md

Selenium .claude/rules/selenium_rules.md

Appium .claude/rules/appium_rules.md
Kiểm tra Page class hiện tại (nếu User chỉ định):
- Đọc file Page class → biết locator đã có sẵn
- Tránh trùng lặp hoặc xung đột naming

Framework	Rule file
Playwright	`.claude/rules/playwright_rules.md`
Selenium	`.claude/rules/selenium_rules.md`
Appium	`.claude/rules/appium_rules.md`

Read the full file on GitHub · 334 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 · 334 lines · 20 tokens per session scan A c7a93d37cf43

Subscribe to this mod's changes

generate_locator is a command published in the GitHub repository anhtester/claude-testing-kit (61 stars, last pushed 2mo ago), licensed MIT. It adds 20 tokens to every session and 3,012 once invoked, about $0.0001 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.

Browser automation Claude Code E2E testing Testing aitesting anhtester claudetestingkit test-automation test-manual

expect

Diff-aware AI browser testing — reads the git diff, maps changes to affected pages via the route map, generates a targeted test plan, and executes it via agent-browser (Rust daemon + CDP, ARIA-tree-first) with pass/fail reporting. Use when testing UI changes, verifying PRs before merge, or running regression checks on…

yonatangross/orchestkit · 73 tokens

claude-testing-kit: Command for Claude Code

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

Copies of this mod

How it starts

/generate_locator — Sinh Locator Ổn Định Cho UI Automation

Input cần từ User

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

Phase 1: Phân tích yêu cầu

What this file has done since we first saw it

Other commands, from other repositories

expect

webapp-testing

record

amazing-e2e-check

verify-pr

monobrowse