What is test_ui_form?

An end-to-end browser test template for submitting a web form, using Playwright, a tool that controls a real browser. It checks both a valid submission and a required-field validation error, with optional screenshots.

Use it to test signup, login, checkout, contact, and other browser-based forms after replacing the placeholders with your app's URLs, selectors, values, and expected messages.

It helps catch problems in the complete user flow that unit tests may miss, such as fields not filling, buttons not working, or success and error messages not appearing.

How bredmond1019/claude-sdk-rs configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to bredmond1019/claude-sdk-rs. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/bredmond1019/claude-sdk-rs/main/.claude/commands/test_ui_form.md

Clone the repo

git clone --depth 1 https://github.com/bredmond1019/claude-sdk-rs

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/bredmond1019/claude-sdk-rs/test_ui_form/github.svg)](https://agentmods.dev/commands/bredmond1019/claude-sdk-rs/test_ui_form)

Your own site

<a href="https://agentmods.dev/commands/bredmond1019/claude-sdk-rs/test_ui_form"><img src="https://agentmods.dev/badge/commands/bredmond1019/claude-sdk-rs/test_ui_form/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/bredmond1019/claude-sdk-rs/test_ui_form"><img src="https://agentmods.dev/badge/commands/bredmond1019/claude-sdk-rs/test_ui_form.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 819 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00819
Opus 5.5	$0.00000	$0.00328
Sonnet 5.5	$0.00000	$0.00164
Haiku 4.5	$0.00000	$0.00082

Measured 11d ago against content hash f0b6ef6730a5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

test_ui_form 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 11d 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.

.claude/commands/test_ui_form.md · 89 lines

How it starts

The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.

E2E Template — UI Form Submit

Test a form submit flow in the browser using Playwright (or playwright-mcp). Replace all {{PLACEHOLDER}} tokens before running.

Setup

App URL: {{BASE_URL}}/{{FORM_PAGE_PATH}} (e.g. http://localhost:3000/signup)
Tool: Playwright (headless) or playwright-mcp for agent-driven browser control.

Test Cases

1. Happy path — valid submit

Navigate to {{BASE_URL}}/{{FORM_PAGE_PATH}}.
Assert the form is visible (look for {{FORM_SELECTOR}} — e.g. form[data-testid="signup"]).
Fill {{FIELD_1_SELECTOR}} with {{FIELD_1_VALID_VALUE}}.
Fill {{FIELD_2_SELECTOR}} with {{FIELD_2_VALID_VALUE}}.
Click the submit button ({{SUBMIT_SELECTOR}}).
Assert success state:
- URL changes to {{SUCCESS_URL}} OR
- A success banner/toast appears matching {{SUCCESS_MESSAGE_TEXT}}.
(Optional) Take a screenshot: screenshot → tests/e2e/screenshots/form-success.png.

2. Validation error — required field empty

Navigate to {{BASE_URL}}/{{FORM_PAGE_PATH}}.
Leave {{REQUIRED_FIELD_SELECTOR}} empty.
Fill all other fields with valid values.
Click submit.
Assert error state:
- Form does NOT navigate away (URL unchanged).
- An inline error message appears near {{REQUIRED_FIELD_SELECTOR}}.
- The error message contains {{REQUIRED_FIELD_ERROR_TEXT}} (or any non-empty error text).
(Optional) Screenshot: tests/e2e/screenshots/form-validation-error.png.

3. Validation error — invalid format

Navigate to {{BASE_URL}}/{{FORM_PAGE_PATH}}.
Fill {{FORMAT_FIELD_SELECTOR}} with {{INVALID_FORMAT_VALUE}} (e.g. notanemail for an email field).
Fill remaining fields validly.
Click submit.
Assert:
- Form does not navigate.
- Error visible near {{FORMAT_FIELD_SELECTOR}}.

4. Server error handling

Simulate a server 500 (intercept the submit network request if using Playwright's page.route(), or bring up a mock server that returns 500).
Submit the form with valid data.
Assert:
- A user-visible error message appears (not a raw stack trace or blank page).
- The form does not silently fail.

Read the full file on GitHub · 89 lines

Changes

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.

11d ago First seen · 89 lines · 0 tokens per session scan A f0b6ef6730a5

Subscribe to this mod's changes

test_ui_form is a command published in the GitHub repository bredmond1019/claude-sdk-rs (23 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 819 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-10-26.

Browser automation E2E testing Testing

test_ui_form next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
test_ui_formbredmond1019/claude-sdk-rs	Command	23	1mo ago	Apache-2.0	A	0	Claude Code
expectyonatangross/orchestkit	Command	299	yesterday	MIT	A	51	Claude Code, Cursor
webapp-testinghamr0/agentic-toolkit	Command	23	6d ago	Apache-2.0	A	35	Claude Code
amazing-e2e-checkbtspoony/mstar-harness	Command	68	yesterday	MIT	A	29	Claude Code
recordMarcosNahuel/antigravity-plugin-cc	Command	32	26d ago	MIT	A	38	Claude Code
verify-prdesplega-ai/qa-use	Command	29	1mo ago	MIT	A	0	Claude Code
auto-verifyInsajin/autopus-adk	Command	111	1mo ago	MIT	A	20	Claude Code

claude-sdk-rs: Command for Claude Code