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.
git clone --depth 1 https://github.com/cassler/awesome-claude-code-setupWrote 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/cassler/awesome-claude-code-setup/visual-test)<a href="https://agentmods.dev/commands/cassler/awesome-claude-code-setup/visual-test"><img src="https://agentmods.dev/badge/commands/cassler/awesome-claude-code-setup/visual-test/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.
<a href="https://agentmods.dev/commands/cassler/awesome-claude-code-setup/visual-test"><img src="https://agentmods.dev/badge/commands/cassler/awesome-claude-code-setup/visual-test.svg" alt="Reviewed on agentmods" width="80" 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.00460 |
| Opus 5.5 | $0.00000 | $0.00184 |
| Sonnet 5.5 | $0.00000 | $0.00092 |
| Haiku 4.5 | $0.00000 | $0.00046 |
Grade A, and why
visual-test 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 1mo 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Visual Testing with Playwright
Use Playwright to visually test your recent UI changes.
MCP Server Integration
If you have the Playwright MCP server configured (via .mcp.json), Claude Code can:
- Navigate to your app and take screenshots
- Interact with elements directly
- Generate Playwright test code
- Run visual comparisons
To use: Simply describe what you want to test and Claude Code will use the Playwright MCP server if available.
Testing Tasks
-
Identify what to test
- List all UI components you've modified
- Note any new user flows or interactions
- Consider responsive design breakpoints
-
Run visual tests
- Use Playwright's screenshot capabilities
- Test in multiple browsers (Chromium, Firefox, WebKit)
- Capture different states (loading, error, success)
- Test both light and dark modes if applicable
-
Interaction testing
- Click through user workflows
- Test form submissions
- Verify animations and transitions
- Check hover states and focus indicators
-
Accessibility checks
- Verify keyboard navigation works
- Test with screen reader announcements
- Check color contrast ratios
- Ensure proper ARIA labels
-
Cross-browser validation
- Compare rendering across browsers
- Test on different viewport sizes
- Verify consistent behavior
Commands to use
Check your project's test scripts and documentation. Common patterns include:
# Examples - adapt to your project's setup:
# npm run test:visual
# yarn test:e2e
# pnpm test:playwright
# python -m pytest tests/visual
# bundle exec rspec spec/features
# ./gradlew test
# For Playwright specifically (if using):
# npx playwright test --update-snapshots
# playwright test --ui
What to look for
- Layout shifts or broken designs
- Missing styles or incorrect colors
- Overlapping elements
- Text that's cut off or wrapped incorrectly
- Interactive elements that don't respond
- Loading states that get stuck
- Error messages that don't display properly
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.
- 1mo ago First seen · 73 lines · 0 tokens per session scan A 3f116dc73cb8
visual-test is a command published in the GitHub repository cassler/awesome-claude-code-setup (268 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 460 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
expect
Diff-aware AI browser testing — reads the git diff, maps changes to affected pages via the route map, generates a targeted test plan, and executes it via agent-browser (Rust daemon + CDP, ARIA-tree-first) with pass/fail reporting. Use when testing UI changes, verifying PRs before merge, or running regression checks on…
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.
record
Record a browser walkthrough of a URL using Antigravity (agy). Generates .webm video, screenshots, and a report. Auto-converts to MP4 if ffmpeg is available.
amazing-e2e-check
Run explicitly requested E2E, browser, device, or installed-deployment scenarios in an independent verification workflow.
verify-pr
Verify a PR's frontend changes through browser automation.
auto-verify
A command for checking a website's front-end user experience with Playwright, a tool that automates web browsers.