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 skills/mengps/huskarui/qmlpreviewernpx skills add mengps/HuskarUI --skill qmlpreviewergit clone --depth 1 https://github.com/mengps/HuskarUIWrote 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/skills/mengps/huskarui/qmlpreviewer)<a href="https://agentmods.dev/skills/mengps/huskarui/qmlpreviewer"><img src="https://agentmods.dev/badge/skills/mengps/huskarui/qmlpreviewer.svg" alt="Measured on agentmods" 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 | $0.00050 | $0.01090 |
| Opus 5 | $0.00025 | $0.00545 |
| Sonnet 5 | $0.00010 | $0.00218 |
| Haiku 4.5 | $0.00005 | $0.00109 |
Grade A, and why
QmlPreviewer 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 5d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- QmlPreviewer — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QML Previewer
Use this skill whenever the agent needs to preview or visually verify a QML UI. Prefer the clipboard capture flow by default, and fall back to launching qmlscene directly when capture is unavailable or unsuitable.
When To Use
Invoke this skill proactively when any of the following is true:
- The agent needs to preview the active QML file to understand the visual result.
- The agent needs to visually verify QML changes it just made or reviewed.
- The agent needs screenshot-based evidence to inspect layout, rendering, clipping, or missing assets.
- The agent needs to confirm whether a QML page loads successfully.
- Visual verification is needed even if the user did not explicitly ask for a preview.
Capabilities
- Auto Detection: Resolve the active QML file from editor context.
- Clipboard Preview: Run the capture script and copy the rendered result to the clipboard.
- Direct Launch: Fall back to
qmlscenewhen clipboard capture is unavailable or unsuitable. - Visual Verification: Report whether the page loads and whether obvious visual problems are present.
- Failure Reporting: Surface path issues, launch failures, and runtime errors.
Critical Rules
These rules are always enforced. Follow them in this order.
File Resolution
- Prefer the active editor file when it is a
.qmlfile. - If multiple files are open, use the focused editor tab.
- If editor context is missing, search for the most relevant recently edited
.qmlfile. - If auto-detection still fails, ask the user once for the QML file path.
Preview Execution
- Use the clipboard capture flow by default.
- Pass absolute paths only for both
qmlscene.exeand the QML file. - Use the direct
qmlscenelaunch only as a fallback when capture is unavailable or unsuitable. - Do not silently skip preview. If preview cannot run, explain why.
Reporting
- Report whether the QML page loads successfully.
- Report obvious layout or rendering issues such as clipping, blank content, missing assets, or unexpected sizing.
- Include runtime or terminal errors when QML fails to launch.
- Be explicit about which flow was used: clipboard capture or direct launch.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 125 lines · 50 tokens per session scan A e3ee15ff0022
QmlPreviewer is a skill published in the GitHub repository mengps/HuskarUI (587 stars, last pushed 11d ago), licensed MIT. It adds 50 tokens to every session and 1,090 once invoked, about $0.0003 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-30.
Other skills, from other repositories
HuskarUI
Queries HuskarUI metadata with Python and guides HuskarUI-first QML/C++ code. Invoke when choosing components, checking examples, or generating HuskarUI UI.
QmlPreviewer
Auto-detects the active QML file from editor context, runs qmlscene, and copies the rendered image to the clipboard by default. Invoke proactively when the agent needs to preview or visually verify a QML UI.
shadcn-vue
Manages shadcn-vue components and projects — adding, searching, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn-vue, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for…
antd
Use when the user's task involves Ant Design (antd) — writing antd components, debugging antd issues, querying antd APIs/props/tokens/demos, migrating between antd versions, or analyzing antd usage in a project. Triggers on antd-related code, imports from 'antd', or explicit antd questions.
compliance
Use when scoping which regulatory frameworks bind a business — SOC 2, ISO 27001, HIPAA, PCI DSS, EU AI Act, DORA, NIS2 — building a control register with owners and evidence, or standing up the cadence that keeps it audit-ready. NOT drafting privacy-policy/ROPA/DPA or ToS text (that is gdpr-privacy, terms-conditions)…
electrik-slate
Build Laravel Blade UI with Electrik Slate 3.x and optional slate-blocks. Use when writing x-slate or x-slate-block components, Livewire forms, tokens, toasts, blocks, or when the user mentions Slate, electrik/slate, electrik/slate-blocks, or slate.electrik.dev.