Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add L3DigitalNet/Claude-Code-Plugins/plugin install qt-suiteWrote 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/l3digitalnet/claude-code-plugins/visual)<a href="https://agentmods.dev/commands/l3digitalnet/claude-code-plugins/visual"><img src="https://agentmods.dev/badge/commands/l3digitalnet/claude-code-plugins/visual/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/l3digitalnet/claude-code-plugins/visual"><img src="https://agentmods.dev/badge/commands/l3digitalnet/claude-code-plugins/visual.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.00040 | $0.01046 |
| Opus 5.5 | $0.00016 | $0.00418 |
| Sonnet 5.5 | $0.00008 | $0.00209 |
| Haiku 4.5 | $0.00004 | $0.00105 |
Grade A, and why
visual 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/qt-suite:visual — Headless GUI Testing
Launch the application headlessly and run visual tests using the Qt Pilot MCP server. Claude interacts with the live UI, verifies behavior, and writes a test report.
Step 1: Prerequisites Check
Run the prerequisites check before attempting to launch:
bash "${CLAUDE_PLUGIN_ROOT}/scripts/check-prerequisites.sh"
If Xvfb is missing, stop and report the install instructions — do not proceed.
Step 2: Find App Entry Point
Determine the application entry point:
- If an argument was provided that looks like a file path (e.g.,
/qt-suite:visual src/main.py), use it. - Read
.qt-test.json— useapp_entryfield if set. - If no config, search for common entry points:
- Glob for
main.py,app.py,__main__.pyin project root andsrc/ - Choose the one that imports
QApplication(Grep forQApplication)
- Glob for
- Resolve to an absolute path.
Step 3: Check If App Is Already Running
Call the Qt Pilot get_app_status MCP tool. If running: true, attach to the existing session. If not running (or crashed), launch fresh.
Step 4: Launch the App
Call launch_app with the resolved entry point:
launch_app(script_path="/abs/path/to/main.py")
Or for module-based apps:
launch_app(module="myapp.main", working_dir="/abs/path/to/project")
Wait for success: true. If launch fails, call get_app_status to retrieve stderr output and report the error with the full stderr content — do not attempt workarounds.
Step 5: Discover the UI
Before testing, always discover available widgets:
find_widgets("*") → lists all named widgets
list_actions() → lists all menu/toolbar actions
If the argument provided describes a specific UI scenario (e.g., "test the file open dialog"), use list_all_widgets to discover the full hierarchy including unnamed elements.
Step 6: Execute the Test Scenario
If a scenario was provided in the argument, execute it. For example, if the user says /qt-suite:visual test the save workflow:
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 · 135 lines · 40 tokens per session scan A 0ef954ff4752
visual is a command published in the GitHub repository L3DigitalNet/Claude-Code-Plugins (8 stars, last pushed 1mo ago), licensed MIT. It adds 40 tokens to every session and 1,046 once invoked, about $0.0002 per session on Opus 5.5. 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-31.
Other commands, from other repositories
playwright-test-heal
Run all my tests and fix the failing ones.
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.
verify-pr
Verify a PR's frontend changes through browser automation.
test-run
Run E2E tests with qa-use CLI.
ui-snapshot.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
laravel-playwright
E2E Playwright patterns; use the laravel:e2e-playwright skill exactly as written.