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/create-smoke-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/create-smoke-test.template)<a href="https://agentmods.dev/commands/evan043/claude-cli-advanced-starter-pack/create-smoke-test.template"><img src="https://agentmods.dev/badge/commands/evan043/claude-cli-advanced-starter-pack/create-smoke-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.01783 |
| Opus 5 | $0.00000 | $0.00892 |
| Sonnet 5 | $0.00000 | $0.00357 |
| Haiku 4.5 | $0.00000 | $0.00178 |
Grade A, and why
create-smoke-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 6d 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 — 249 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.
description: Auto-generate Playwright smoke tests for critical user flows
Create Smoke Test
Generate Playwright E2E tests automatically by analyzing your application's routes and components.
Usage
/create-smoke-test
/create-smoke-test --page login
/create-smoke-test --flow checkout
/create-smoke-test --category deploy-regression
/create-smoke-test --category auth-flow
/create-smoke-test --category route-loading
What It Does
- Analyze Routes - Discover pages from router configuration
- Identify Flows - Map critical user journeys
- Generate Tests - Create Playwright test files
- Add Selectors - Include data-testid recommendations
Smoke Test Categories
Authentication
- Login flow
- Logout flow
- Password reset
- Session persistence
Navigation
- Home page loads
- All routes accessible
- Navigation links work
- 404 handling
Critical Paths
- User registration
- Core feature usage
- Payment flow (if applicable)
- Data submission forms
Deploy Regression
- API endpoint existence verification
- Response shape validation (required fields present)
- Status code contracts (expected codes match)
- CORS header checks on preflight
- Pagination parameter handling
- Template:
templates/testing/deploy-regression.spec.template.ts
Auth Flow
- Login sets cookie/token correctly
- Session persists across page reload
- Invalid credentials show error message
- Protected routes redirect to login when unauthenticated
- Logout clears all auth state
- Expired token triggers refresh (no infinite loop)
- Template:
templates/testing/auth-flow.spec.template.ts
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.
- 6d ago First seen · 249 lines · 0 tokens per session scan A b6fd7ac78001
create-smoke-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 1,783 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-08-30.
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.