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-smoke.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-smoke.template)<a href="https://agentmods.dev/commands/evan043/claude-cli-advanced-starter-pack/ui-smoke.template"><img src="https://agentmods.dev/badge/commands/evan043/claude-cli-advanced-starter-pack/ui-smoke.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.00550 |
| Opus 5 | $0.00000 | $0.00275 |
| Sonnet 5 | $0.00000 | $0.00110 |
| Haiku 4.5 | $0.00000 | $0.00055 |
Grade A, and why
ui-smoke.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 — 70 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-smoke — Codex Runtime
Run smoke tests via shell. Playwright MCP is unavailable in Codex.
# Run only smoke-tagged tests
npx playwright test --grep "smoke"
# Or run the smoke test suite file directly
npx playwright test e2e/smoke.spec.ts
If no smoke tests exist yet, tell me and I'll generate a basic smoke test file.
For Playwright MCP browser integration, use Claude Code CLI: /ui-smoke
description: Run quick Neovim UI smoke test for nvim-ccasp
Neovim UI Smoke Test
Run a fast smoke test that opens the CCASP UI, traverses key menu items, opens popouts, validates windows/buffers, then closes cleanly.
Usage
/ui-smoke
What It Does
- Launch nvim headless with ccasp plugin
- Call
require("ccasp").setup({layout="appshell"})andopen() - Verify icon rail, header, and footer windows exist
- Toggle flyout for each of the 5 sections
- Toggle right panel on/off
- Close everything and verify clean state (no lingering floats)
Pass/Fail Criteria
- PASS: All steps complete, no Lua errors, no orphaned windows
- FAIL: Any step throws, windows don't appear, or cleanup leaves orphans
Running
./scripts/nvim-smoke.ps1
Protocol
When the user runs /ui-smoke:
- Execute
./scripts/nvim-smoke.ps1 - Parse output for PASS/FAIL
- If FAIL: capture snapshot, show exact failure step
- If PASS: report clean result with timing
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 · 70 lines · 0 tokens per session scan A 4001fe1bbd6d
ui-smoke.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 550 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
verify-loop
A command that repeatedly checks recent code changes and tries to fix failures, with a configurable retry limit. It can run code review, builds, tests, linting, and type checks according to the project language.
web-checklist
A checklist command for testing a website after a Git merge. It records checklist items in a file so progress can be viewed and individual checks can be marked complete.
test-suite
Run comprehensive test suite with coverage analysis.
e2e
Generate and run end-to-end tests with Playwright. Creates test journeys, runs tests, captures screenshots/videos/traces, and uploads artifacts.
test
Execute comprehensive test suites (unit, integration, e2e) to validate implementation correctness and quality.
e2e-echo-command
E2E test command — echoes back the user message.