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 vosslab/vosslab-skills --skill pyside6-engineergit clone --depth 1 https://github.com/vosslab/vosslab-skillsWrote 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/vosslab/vosslab-skills/pyside6-engineer)<a href="https://agentmods.dev/skills/vosslab/vosslab-skills/pyside6-engineer"><img src="https://agentmods.dev/badge/skills/vosslab/vosslab-skills/pyside6-engineer/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/vosslab/vosslab-skills/pyside6-engineer"><img src="https://agentmods.dev/badge/skills/vosslab/vosslab-skills/pyside6-engineer.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.00055 | $0.01299 |
| Opus 5 | $0.00028 | $0.00649 |
| Sonnet 5 | $0.00011 | $0.00260 |
| Haiku 4.5 | $0.00006 | $0.00130 |
Grade A, and why
pyside6-engineer 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 9d 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.
This is a copy
86% identical to vuln-assessment-phase — 126 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PySide6 Engineer
Overview
Use this skill to build desktop interfaces that are technically sound with PySide6.
Focus on widget architecture, signal-slot design, state management, and Qt best practices.
Use the official Qt for Python docs as the primary source for APIs, examples, and tool behavior.
For UI/UX review and design polish, use the ui-ux-engineer skill.
Workflow
- Detect the project shape before coding.
- Inspect the target for existing PySide6 source: window or widget classes,
.uifiles, signal-slot wiring, and any GUI tests or screenshots. - If GUI code exists, follow the existing-app path: inventory the current widgets and state flow, then make targeted, layout-preserving changes tied to a specific issue.
- If no GUI code exists, follow the greenfield path: decide the window shell and primary surface first, then build the layout and hierarchy before wiring behavior.
- Read
references/project_workflow.mdfor the full two-path workflow: greenfield (evidence, Qt contract, implementation choices, validation) and existing-repo (inspect first, identify current design, targeted changes, prove improvement).
- Classify the surface before coding.
- Read
references/topic_index.mdas the routing front door: match the user problem to a row to find the right reference guide before writing any code. - Decide whether the work belongs in Qt Widgets or Qt Quick first, then decide whether it should use a
QMainWindow,QWidget,QDialog, wizard, dock layout, or model/view surface. - Read
references/task_selection.mdto classify underspecified requests by window container, state coordination model, user goal, and required states. - Identify the primary user goal, the main workflow path, and the states that must be handled: loading, empty, valid, invalid, busy, success, and failure.
- Read
references/official_qt_for_python_docs.mdwhen you need the official entry points for installation, module lookup, tutorials, examples, or package tools.
What ships with it
13 files 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.
- agents/openai.yaml 247 B
- references/deployment_and_packaging.md 1.4 KB
- references/designer_ui_workflow.md 1.6 KB
- references/local_books.md 3.4 KB
- references/model_view.md 1.7 KB
- references/official_qt_for_python_docs.md 2.2 KB
- references/project_workflow.md 5.6 KB
- references/pyside6_patterns.md 4.3 KB
- references/reference_survey.md 5.7 KB
- references/signals_slots.md 1.6 KB
- references/task_selection.md 3.5 KB
- references/testing_and_oracles.md 5.3 KB
- references/topic_index.md 4.8 KB
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.
- 9d ago First seen · 79 lines · 55 tokens per session scan A 793acec2cdd1
pyside6-engineer is a skill published in the GitHub repository vosslab/vosslab-skills (2 stars, last pushed 14d ago), licensed MIT. It adds 55 tokens to every session and 1,299 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to vuln-assessment-phase, differing in 126 lines, and is treated as a copy.
Other skills, from other repositories
huggingface-gradio
Build Gradio web UIs and demos in Python. Use when creating or editing Gradio apps, components, event listeners, layouts, or chatbots.
shiny-for-python
Building, styling, testing, debugging, or observing a Shiny for Python (py-shiny) reactive web app - from shiny import ..., shiny run app.py. Index skill: read this, then open the linked reference for the task. Covers dashboard design and visual QA; card toolbars and accessible icons; interactive Plotly charts and…
gpui-toolkit
Use when building or modifying GPUI applications in the gpui-toolkit workspace, especially when choosing reusable toolkit crates, composing UI, adding components, charts, themes, layouts, audio controls, mobile surfaces, or validation coverage. Prefer existing toolkit APIs over custom one-off implementations.
fast-dash
Build a Fast Dash web app from a Python function. Use when the user wants to turn a function into an interactive app, add a UI to an existing function, or build a dashboard / form / wizard. Fast Dash infers UI components from type hints, so a well-typed function becomes an app with one decorator.
streamlit
Streamlit Python web application framework. Covers session state, caching, layouts, widgets, multipage apps, and deployment. Use when building interactive Python data apps or dashboards. USE WHEN: user mentions "streamlit", "st.sessionstate", "st.cachedata", "streamlit app", "python dashboard", "python web app"…
textual-builder
Build Text User Interface (TUI) applications using the Textual Python framework (v0.86.0+). Use when creating terminal-based applications, prototyping card games or interactive CLIs, or when the user mentions Textual, TUI, or terminal UI. Includes comprehensive reference documentation, card game starter template, and…