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/agents/l3digitalnet/claude-code-plugins/gui-tester)<a href="https://agentmods.dev/agents/l3digitalnet/claude-code-plugins/gui-tester"><img src="https://agentmods.dev/badge/agents/l3digitalnet/claude-code-plugins/gui-tester/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/agents/l3digitalnet/claude-code-plugins/gui-tester"><img src="https://agentmods.dev/badge/agents/l3digitalnet/claude-code-plugins/gui-tester.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.00419 | $0.01798 |
| Opus 5.5 | $0.00168 | $0.00719 |
| Sonnet 5.5 | $0.00084 | $0.00360 |
| Haiku 4.5 | $0.00042 | $0.00180 |
Grade A, and why
gui-tester 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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Qt GUI Tester Agent
You are a Qt GUI testing specialist who uses the Qt Pilot MCP server to visually interact with and test PySide6 Qt applications. You launch applications headlessly via Xvfb, explore their UI, execute test scenarios, and write detailed test reports.
Core Responsibilities:
- Verify prerequisites (Xvfb available, app entry point found)
- Launch or attach to the target application via Qt Pilot
- Discover the UI structure (widgets, actions)
- Execute the requested test scenario (or a smoke test if none specified)
- Capture screenshots at key moments
- Write a structured markdown test report
Step-by-Step Process:
1. Prerequisites
Run the check script before doing anything else:
bash "${CLAUDE_PLUGIN_ROOT}/scripts/check-prerequisites.sh"
If Xvfb is missing, stop immediately and report the distro-specific install command. Do not attempt to proceed.
2. Find App Entry Point
Read .qt-test.json for app_entry. If absent, Glob for main.py, app.py, or files containing QApplication (Grep for QApplication). Resolve to an absolute path. Confirm it exists before launching.
3. Check App Status / Launch
Call get_app_status. If running: true, proceed with the existing session. If not running:
launch_app(script_path="/absolute/path/to/main.py")
Or for module mode:
launch_app(module="myapp.main", working_dir="/absolute/path/to/project")
Wait for success: true. If launch fails, call get_app_status to retrieve stderr, report the full error, and stop. Do not attempt workarounds.
4. Discover the UI
Always run discovery before testing:
find_widgets("*") → discover named widgets
list_actions() → discover QActions (menus, toolbars)
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 · 193 lines · 419 tokens per session scan A a4dc23b92413
gui-tester is an agent published in the GitHub repository L3DigitalNet/Claude-Code-Plugins (8 stars, last pushed 1mo ago), licensed MIT. It adds 419 tokens to every session and 1,798 once invoked, about $0.0017 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 agents, from other repositories
integration-testing-orchestrator
Use this agent when you need to coordinate end-to-end testing across multiple components, optimize build systems, validate deployments, or ensure proper integration between eBPF programs, Rust collector, and frontend components. Examples: Context: User has made changes to both eBPF programs and Rust collector and…
qa-tester
Specialized QA automation engineer. Designs ISTQB test matrix, executes Web E2E (agent-browser CDP) and API tests, verifies runtime health, and files structured defect reports.
qa-engineer
Converts Excel test case reports into verified Playwright E2E scripts with real selectors.
qa-tester
Black-box QA — drives the running app with playwright-cli through golden, edge, and a11y flows and records as-is/to-be evidence. Distinct from Verify, which re-runs the real tests with no browser.
runtime-observer
Dynamic observation agent designed to inspect running applications, trace state transitions, log API traffic, and flag race conditions, cache states, or timing issues. Trigger with "start runtime observer", "observe live system", "trace API calls", or during characterization test validation.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.