Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/evan043/claude-cli-advanced-starter-packnpx agentmods add commands/evan043/claude-cli-advanced-starter-pack/ui-test.templateWrote 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/evan043/claude-cli-advanced-starter-pack/ui-test.template)<a href="https://agentmods.dev/commands/evan043/claude-cli-advanced-starter-pack/ui-test.template"><img src="https://agentmods.dev/badge/commands/evan043/claude-cli-advanced-starter-pack/ui-test.template.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.1 | $0.00000 | $0.00890 |
| Opus 5 | $0.00000 | $0.00445 |
| Sonnet 5 | $0.00000 | $0.00178 |
| Haiku 4.5 | $0.00000 | $0.00089 |
Grade A, and why
ui-test.template 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.
How it starts
The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Runtime Compatibility
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows:
AskUserQuestion=> ask the user directly in chat.WebSearch/WebFetch=> use available web tools (search_query,open,find) and cite links.Read/Write=> use shell/filesystem tools in this workspace.- Claude-only MCP calls (for example Playwright MCP names) => use available equivalents or clearly state fallback.
- Keep intent and output format identical; only adapt execution mechanics.
ui-test — Codex Runtime
This command runs Playwright E2E tests. Playwright MCP is unavailable in Codex, but I can run tests via shell if Playwright is installed.
Run Tests via Shell
# Run all E2E tests
npx playwright test
# Run with headed browser (if display available)
npx playwright test --headed
# Run specific test file
npx playwright test tests/auth.spec.ts
# Run with specific grep pattern
npx playwright test --grep "login"
View Test Results
# Show HTML report
npx playwright show-report
# Show test output in terminal
npx playwright test --reporter=list
Tell me which tests to run and I'll execute them via shell commands.
For Playwright MCP integration with visual browser control, use Claude Code CLI: /ui-test
description: Run Neovim UI tests for the nvim-ccasp plugin
Run Neovim UI Tests
Execute the full plenary.nvim test suite for the nvim-ccasp Neovim plugin, covering smoke tests, keymap validation, and layout structure verification.
Usage
/ui-test
/ui-test --filter smoke
/ui-test --filter keymaps
/ui-test --filter layout
What It Does
- Detect Environment - Verify nvim and plenary.nvim are available
- Run Tests - Execute headless Neovim tests via PlenaryBusted
- Report Results - Parse output and display pass/fail summary
- Capture Artifacts - Save layout snapshots on failure
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 · 123 lines · 0 tokens per session scan A e4cc07a111c5
ui-test.template is a command published in the GitHub repository evan043/claude-cli-advanced-starter-pack (61 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 890 tokens. 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-09-03.
Other commands, from other repositories
qawolf-cli
Manage QA Wolf through the qawolf CLI. Use when asked to create, update, or list coverage requests, bug reports, or maintenance reports; start a run of flows or tags on the QA Wolf platform or read a run's results; list, set, or delete environment variables; manage environments, flows, or tags; request automation of…
web-checklist
머지 후 웹 테스트 체크리스트 + 완료 추적 (v6).
test-suite
Run comprehensive test suite with coverage analysis.
auto-verify
프론트엔드 UX 검증 — Playwright 기반 비주얼 검증을 실행합니다.
check-ux
Walk the key flows in a real browser at mobile and desktop viewports, then a task per friction point.
e2e
Generate and run end-to-end tests with Playwright. Creates test journeys, runs tests, captures screenshots/videos/traces, and uploads artifacts.