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.
npx agentmods add agents/l3digitalnet/claude-code-plugins/gui-testergit clone --depth 1 https://github.com/L3DigitalNet/Claude-Code-PluginsWhat 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 | $0.00419 | $0.01798 |
| Opus 5 | $0.00210 | $0.00899 |
| Sonnet 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 2d 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.
- 2d 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 (6 stars, last pushed 2d ago), licensed MIT. It adds 419 tokens to every session and 1,798 once invoked, about $0.0021 per session on Opus 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.