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 commands/sukirman1901/frontend-expert/test-uigit clone --depth 1 https://github.com/sukirman1901/frontend-expertWrote 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/sukirman1901/frontend-expert/test-ui)<a href="https://agentmods.dev/commands/sukirman1901/frontend-expert/test-ui"><img src="https://agentmods.dev/badge/commands/sukirman1901/frontend-expert/test-ui.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.00018 | $0.00291 |
| Opus 5 | $0.00009 | $0.00146 |
| Sonnet 5 | $0.00004 | $0.00058 |
| Haiku 4.5 | $0.00002 | $0.00029 |
Grade A, and why
test-ui 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 5d 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
Invoke the test-engineer agent.
Skills to load (in order)
frontend-testingui-componentsaccessibilityfe-devtools— Lighthouse/axe/viewport when evidence is requiredanti-ai-slop— only if verifying visual regressions tied to slop fixesfrontend-judgment— only if test strategy for a large surface is unclear
Modes
/test-ui— test current / recently changed UI/test-ui --component <name>— focus one component/test-ui --tdd— red-green-refactor for new behavior/test-ui --gaps— report missing coverage only
$ARGUMENTS selects the mode and options.
What to do
- Publish a short test plan (unit / integration / E2E)
- Prefer TDD for new behavior
- Cover loading / error / empty when those states exist
- Prefer role/label queries over test IDs
- Add a11y assertions when tooling exists
- Run the project's test command when available
- Report coverage checklist + remaining gaps (per test-engineer output format)
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.
- 5d ago First seen · 34 lines · 18 tokens per session scan A 0339a0c35c32
test-ui is a command published in the GitHub repository sukirman1901/frontend-expert (10 stars, last pushed 2d ago), licensed MIT. It adds 18 tokens to every session and 291 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
playwright
Write or update Playwright E2E tests following project conventions.
e2e
使用 Playwright 对 Web UI 进行端到端测试（支持视频录制、Trace 录制、控制台/网络日志捕获）.
paul:verify
Guide manual user acceptance testing of recently built features.
plan-spec
仅在人工明确安排 UI 自动化时，根据任务、产品规则或原型生成独立行为 Spec.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
ui-snapshot.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.