Borrowing it
Nothing to install: this file belongs to cbmono/ai-setup. 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/cbmono/ai-setup/main/.claude/skills/test-locators/SKILL.mdgit clone --depth 1 https://github.com/cbmono/ai-setupWrote 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/skills/cbmono/ai-setup/test-locators)<a href="https://agentmods.dev/skills/cbmono/ai-setup/test-locators"><img src="https://agentmods.dev/badge/skills/cbmono/ai-setup/test-locators/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/skills/cbmono/ai-setup/test-locators"><img src="https://agentmods.dev/badge/skills/cbmono/ai-setup/test-locators.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.00059 | $0.00450 |
| Opus 5.5 | $0.00024 | $0.00180 |
| Sonnet 5.5 | $0.00012 | $0.00090 |
| Haiku 4.5 | $0.00006 | $0.00045 |
Grade A, and why
test-locators 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 2mo 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.
What it actually says
Stable test locators for frontend
When you create or modify user-facing UI, add a stable test locator to every element a test or user would interact with or assert on — buttons, links, inputs, selects, checkboxes, form containers, list items, modals, toasts, and anything with dynamic state. These become the handles QA uses in automation; without them E2E tests latch onto CSS classes, DOM position, or text and break on the next refactor.
What to add
- A test attribute:
data-testid, ordata-testif that's already the project's convention. Match what existing components use — grep a few siblings first; never mix both in one codebase. - Where they fit naturally, semantic/accessibility handles too:
label,aria-label,name,id,role. These serve screen readers and double as stable locators.
Naming
Format: <feature-or-section>-<element>-<purpose>, lowercase kebab-case, by business meaning.
- Good:
login-submit-button,registration-country-card-de,checkout-payment-submit-button,user-profile-save-button,disclosure-legal-documents-checkbox - Bad:
button1,test,blue-button,right-panel-button,country-card-0,checkbox-1
Avoid encoding position/index (-0, -1), color, CSS class, component-library names, or random numbers — they break when layout, styling, or order changes. Prefer a stable business identifier: country-card-de, not country-card-0.
When to skip
Purely decorative, static, non-asserted elements (spacers, presentational wrappers, icons) don't need a locator. Don't blanket every <div> — aim for the elements a test would realistically target.
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.
- 2mo ago First seen · 27 lines · 59 tokens per session scan A d5ee7b8e29df
test-locators is a skill published in the GitHub repository cbmono/ai-setup (2 stars, last pushed 10d ago), licensed MIT. It adds 59 tokens to every session and 450 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-31.
Other skills, from other repositories
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.