Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/cbmono/ai-setup/test-locatorsnpx skills add cbmono/ai-setup --skill test-locatorsgit 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.svg" alt="Measured on agentmods" 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 | $0.00059 | $0.00450 |
| Opus 5 | $0.00030 | $0.00225 |
| Sonnet 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 3d 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.
- 3d 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.0003 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 skills, from other repositories
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
verify
Exercise the real app/API/CLI and collect observable evidence; tests alone do not count as end-to-end verification.
solopi-ai
通过 SoloPi 的机器可读 CLI 编译和执行 AI 验证计划，管理签名端侧 ExecuTorch 决策模型、持久设备池、无人值守任务、安卓设备、应用、动作、配置、用例步骤与交互录制、回放及性能历史、动态 Agent、批量与重复执行、性能监控、压力测试和证据。适用于需求/AC 到 Result Judge 三态结论、cloud/on-device 决策切换、模型发布门禁，以及 generation 租约的多设备 CI 执行。.
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.
local-frontend-check
Smoke-test or verify UI behaviour on the local Jarvis Registry frontend running at http://localhost/gateway. Use for manual regression checks, bug-fix verification, and end-to-end confirmation of specific flows without running the automated test suite.
pr-integration-test
Design, implement, and validate Intelligent Terminal integration tests for a target pull request or regression. Use when asked to add PR integration tests, convert a bug fix into E2E coverage, prove existing behavior still works, map tests to the release checklist, or verify E2E reports mark checklist cases complete.