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 skills add loonghao/auroraview --skill qt-to-auroraview-migrationgit clone --depth 1 https://github.com/loonghao/auroraviewWrote 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/loonghao/auroraview/qt-to-auroraview-migration)<a href="https://agentmods.dev/skills/loonghao/auroraview/qt-to-auroraview-migration"><img src="https://agentmods.dev/badge/skills/loonghao/auroraview/qt-to-auroraview-migration/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/skills/loonghao/auroraview/qt-to-auroraview-migration"><img src="https://agentmods.dev/badge/skills/loonghao/auroraview/qt-to-auroraview-migration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
SkillSpector: 2 findings, up to low
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- low MCP Rug Pull · line 66 pip install without ==version installs the latest release, which could include malicious changes.Fix: Pin the version: pip install package==1.2.3
- low MCP Rug Pull · line 191 pip install without ==version installs the latest release, which could include malicious changes.Fix: Pin the version: pip install package==1.2.3
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.00104 | $0.02752 |
| Opus 5.5 | $0.00042 | $0.01101 |
| Sonnet 5.5 | $0.00021 | $0.00550 |
| Haiku 4.5 | $0.00010 | $0.00275 |
Grade A, and why
qt-to-auroraview-migration 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 2mo 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 — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Qt → AuroraView migration skill
This skill turns an existing Qt-based Python project (typically one that uses
QWebEngineView, a custom QMainWindow, or a DCC tool dialog with embedded HTML)
into an AuroraView project with:
- A native Rust-powered WebView (~5 MB vs ~120 MB Qt WebEngine)
- Unified
create_webview()entry point (standalone / Qt parent / HWND) - Bidirectional Python ↔ JavaScript bridge (
webview.emit/@webview.on) - Full MCP control out of the box via
dcc-mcp-core's gateway — every AuroraView window registers itself into the gateway and exposes a CDP bridge, so agents can click, fill, screenshot, and call Python APIs over standard MCP without the user writing any Python glue
When to use this skill
Use it when you see any of these signals in the source project:
from PySide6.QtWebEngineWidgets import QWebEngineView(or PySide2 / PyQt5 / PyQt6)QWebChannel+registerObjectfor JS↔Python IPC- A DCC-embedded Qt dialog that loads an HTML/React/Vue frontend
- A
QMainWindowwhose central widget is basically a browser - The user says "convert/migrate/port this Qt tool to AuroraView" or "I want to control this Qt app with MCP"
Decision tree
Is there a QWidget parent (Maya/Houdini/Nuke/3ds Max)?
├── Yes → use QtWebView path (create_webview(parent=qwidget, ...))
└── No
├── Is there a native HWND (Unreal, C++ host)?
│ └── Yes → use HWND path (create_webview(parent=hwnd, ...))
└── No → standalone (create_webview(url=..., ...))
All three paths return the same WebView API; only the parent argument differs.
Migration playbook
Perform these steps in order. Each has a concrete before/after snippet so you can grep-and-replace safely.
Step 1 — Dependencies
Replace Qt WebEngine with AuroraView. Keep qtpy / a Qt binding only if the
tool still needs Qt widgets around the webview (toolbars, dock panels, DCC
integration).
# pyproject.toml — remove
# "PySide6-WebEngine"
# "PyQtWebEngine"
# "auroraview-mcp" # the standalone Python MCP pkg was retired; see #364
# pyproject.toml — add
"auroraview>=0.4.19" # core
"auroraview[qt]>=0.4.19" # if embedding inside a Qt host
# MCP control now comes from dcc-mcp-core's gateway + auroraview-cli; no extra
# Python dep is needed on the project itself. Install the tooling separately:
# pip install dcc-mcp-core # gateway + skill runtime (PyPI)
# auroraview-cli skills install --target cursor # wire agent tools
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.
- 2mo ago First seen · 268 lines · 104 tokens per session scan A d4e36f2e2ba0
qt-to-auroraview-migration is a skill published in the GitHub repository loonghao/auroraview (47 stars, last pushed 1mo ago), licensed MIT. It adds 104 tokens to every session and 2,752 once invoked, about $0.0004 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-30.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.