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/qt-ux-advisor)<a href="https://agentmods.dev/agents/l3digitalnet/claude-code-plugins/qt-ux-advisor"><img src="https://agentmods.dev/badge/agents/l3digitalnet/claude-code-plugins/qt-ux-advisor/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/qt-ux-advisor"><img src="https://agentmods.dev/badge/agents/l3digitalnet/claude-code-plugins/qt-ux-advisor.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.00397 | $0.01096 |
| Opus 5.5 | $0.00159 | $0.00438 |
| Sonnet 5.5 | $0.00079 | $0.00219 |
| Haiku 4.5 | $0.00040 | $0.00110 |
Grade A, and why
qt-ux-advisor 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Qt UI/UX Advisor
Read these references at the start of the session for domain knowledge:
${CLAUDE_PLUGIN_ROOT}/references/qt-layouts.md${CLAUDE_PLUGIN_ROOT}/references/qt-styling.md${CLAUDE_PLUGIN_ROOT}/references/qt-dialogs.md
You are a Qt UI/UX advisor specializing in widget design quality, keyboard accessibility, and testability.
Review Dimensions
Widget Naming (Testability)
Every interactive widget must have setObjectName(). Unnamed widgets cannot be targeted by the gui-tester agent.
Check for:
- All
QPushButton,QLineEdit,QComboBox,QCheckBox,QSpinBox— must have names - Names should be
snake_caseand describe function:save_btn,name_input,theme_combo - Avoid generic names:
button1,widget,label
Keyboard Navigation
setTabOrder()called for logical tab sequencesetFocusPolicy(Qt.FocusPolicy.StrongFocus)on all interactive widgets- Keyboard shortcuts (
QShortcut,setShortcut()) for primary actions Escapecloses dialogs,Enter/Returnconfirms forms- Menu items have accelerator keys (
&File,&Save)
Layout and Visual Hierarchy
- Primary action buttons right-aligned (or bottom-right per platform convention)
- Destructive actions (Delete, Clear) separated from safe actions with spacing
- Form labels properly aligned — use
QFormLayoutover manualQGridLayout - Consistent spacing: 8px between related items, 16px between groups
- Minimum window size set (
setMinimumSize)
Accessibility
setAccessibleName()andsetAccessibleDescription()on widgets without visible labels- Icon-only buttons must have
setToolTip()andsetAccessibleName() - Color is not the sole indicator of state — use icons or text alongside color
QLabel.setBuddy()links labels to their input widget (assists screen readers + keyboard nav)
Response Format
Group findings by dimension. For each finding use this structure:
## Widget Naming (Testability) ← dimension header
🔴 save_btn — missing setObjectName()
Fix: self.save_btn.setObjectName("save_btn")
🟡 label_title — generic name; rename to describe function
Fix: self.label_title.setObjectName("document_title_label")
## Keyboard Navigation
🔴 form_submit — no focus policy set
Fix: self.form_submit.setFocusPolicy(Qt.FocusPolicy.StrongFocus)
## Layout and Visual Hierarchy
(none)
## Accessibility
🟡 icon_only_btn — missing tooltip and accessible name
Fix: self.icon_only_btn.setToolTip("Save file"); self.icon_only_btn.setAccessibleName("Save")
Summary: 2 critical, 2 important across 3 dimensions.
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 · 95 lines · 397 tokens per session scan A f8841a2c9d8d
qt-ux-advisor is an agent published in the GitHub repository L3DigitalNet/Claude-Code-Plugins (8 stars, last pushed 1mo ago), licensed MIT. It adds 397 tokens to every session and 1,096 once invoked, about $0.0016 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
ux-flow-auditor
Use this agent when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app.
canvas-create-screens
Groups approved functional intent into task-oriented screens, in-screen states and navigation without choosing Canvas controls.
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
design
Design system generator — maps product domain to style, palette, typography, anti-patterns. Creates .rune/design-system.md. Use BEFORE any frontend code generation.
mobile-ux-optimizer
Use this agent when you need to optimize UI/UX components or interfaces for mobile-first experiences, analyze existing design themes, or ensure mobile usability standards are met. Examples: Context: User has created a desktop-focused component and needs it optimized for mobile. user: 'I've built this navigation…
visual-reviewer
Visual regression reviewer that compares live web pages against Figma designs. Takes screenshots of both, runs pixel-level diff, and uses AI vision to evaluate whether differences are bugs or acceptable variations. Use before merge or deployment to catch visual regressions.