pyside6-engineer

pyside6-engineer is a skill for Claude Code, Codex from vosslab/vosslab-skills. It costs 55 tokens per session (1,299 once invoked), scanned A, a copy of vuln-assessment-phase, MIT.

A set of instructions for building and reviewing PySide6 desktop applications, which are computer programs with graphical windows and controls made in Python.

In plain words
What is it for?
Creating or improving PySide6 widgets, dialogs, tables, themes, validation, signal-and-slot event wiring, and threaded work.
Why use it?
It helps organize windows, forms, navigation, application state, and user actions without losing track of how the interface behaves.

Skill for Claude CodeCodex

Written for Claude Code and Codex: shipped in a Claude Code plugin, but also agents/openai.yaml present. Also seen: mentions subagents.

Part of the vosslab-skills plugin — 42 skills, 14 agents shipped together

Good fit Creating or improving PySide6 widgets, dialogs, tables, themes, validation, signal-and-slot event wiring, and threaded work.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/vosslab/vosslab-skills/pyside6-engineer
Install

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.

Any agent
npx skills add vosslab/vosslab-skills --skill pyside6-engineer
Clone the repo
git clone --depth 1 https://github.com/vosslab/vosslab-skills

Made for: Claude Code, Codex.

Or install vosslab-skills, the plugin that ships this one along with the rest of its 42 skills, 14 agents.

Wrote 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.

agentmods badge for pyside6-engineer

README.md
[![agentmods](https://agentmods.dev/badge/skills/vosslab/vosslab-skills/pyside6-engineer/github.svg)](https://agentmods.dev/skills/vosslab/vosslab-skills/pyside6-engineer)
Your own site
<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.

agentmods 80×15 button for pyside6-engineer

Your own site · 80×15
<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>
Per session 55 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,299 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 86% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 9d ago against content hash 793acec2cdd1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

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.

Origin

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.

skills/experts/pyside6-engineer/SKILL.md · 79 lines

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

  1. Detect the project shape before coding.
  • Inspect the target for existing PySide6 source: window or widget classes, .ui files, 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.md for the full two-path workflow: greenfield (evidence, Qt contract, implementation choices, validation) and existing-repo (inspect first, identify current design, targeted changes, prove improvement).
  1. Classify the surface before coding.
  • Read references/topic_index.md as 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.md to 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.md when you need the official entry points for installation, module lookup, tutorials, examples, or package tools.

Read the full file on GitHub · 79 lines

Changes

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.

  1. 9d ago First seen · 79 lines · 55 tokens per session scan A 793acec2cdd1

Subscribe to this mod's changes

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.

Related

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.

huggingface/skills · 37 tokens

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…

posit-dev/py-shiny · 209 tokens

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.

pierreaubert/gpui-toolkit · 60 tokens

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.

dkedar7/fast_dash · 69 tokens

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"…

claude-dev-suite/claude-dev-suite · 107 tokens

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…

YPares/agent-skills · 73 tokens