Borrowing it
Nothing to install: this file belongs to Community-Access/accessibility-agents. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Community-Access/accessibility-agents/main/.gemini/extensions/a11y-agents/skills/wxpython-specialist/SKILL.mdgit clone --depth 1 https://github.com/Community-Access/accessibility-agentsWrote 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/community-access/accessibility-agents/wxpython-specialist)<a href="https://agentmods.dev/skills/community-access/accessibility-agents/wxpython-specialist"><img src="https://agentmods.dev/badge/skills/community-access/accessibility-agents/wxpython-specialist.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.1 | $0.00000 | $0.01939 |
| Opus 5 | $0.00000 | $0.00970 |
| Sonnet 5 | $0.00000 | $0.00388 |
| Haiku 4.5 | $0.00000 | $0.00194 |
Grade A, and why
wxpython-specialist 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 3d 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
wxPython Specialist
wxPython GUI expert covering sizer layouts, event handling, AUI framework, custom controls, threading (wx.CallAfter/wx.PostEvent), dialog design, menu/toolbar construction, and desktop accessibility (screen readers, keyboard navigation). Covers cross-platform gotchas for Windows and macOS.
Core Principles
- Sizers, always. Never use absolute positioning.
- Events, not polling. Bind events properly.
- Thread safety is non-negotiable. Use
wx.CallAfter()orwx.PostEvent()from worker threads. - Accessibility is built in. Every control must be keyboard-accessible with proper names.
- Cross-platform by default. Know the Windows/macOS differences.
Sizer Layouts
wx.BoxSizer(wx.VERTICAL/wx.HORIZONTAL)for stack or row layoutswx.GridBagSizer(vgap, hgap)for form layoutswx.SizerFlags(proportion).Expand().Border(wx.ALL, border)modern API- Proportion: 0 = minimum size, 1+ = takes remaining space
wx.EXPANDfills the non-main axis- Always call
self.SetSizerAndFit(sizer)
Event Handling
self.Bind(wx.EVT_BUTTON, self.handler, self.btn)standard bindingwx.lib.newevent.NewEvent()for custom event typeswx.PostEvent(target, evt)for thread-safe event postingevent.Skip()to let other handlers also process the event- Always handle
wx.EVT_CLOSEfor cleanup
Screen Reader Key Event Pitfalls
Screen readers like NVDA and JAWS install a low-level keyboard hook (WH_KEYBOARD_LL) that intercepts every keystroke system-wide before any window message reaches the application. When the screen reader consumes a key (e.g., Enter on a focused wx.ListBox), the WM_KEYDOWN message never arrives -- so EVT_KEY_DOWN and EVT_CHAR handlers silently fail.
Why EVT_CHAR_HOOK works: Even when WM_KEYDOWN does arrive, native Win32 controls (ListBox, TreeView, ListView) may process the message in their own WndProc before wxPython generates EVT_KEY_DOWN. EVT_CHAR_HOOK fires at the top-level window within wxWidgets' own event processing, before the native control handler runs.
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.
- 3d ago First seen · 150 lines · 0 tokens per session scan A 582b1eb9fcc1
wxpython-specialist is a skill published in the GitHub repository Community-Access/accessibility-agents (405 stars, last pushed 26d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,939 tokens. 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-09-03.
Other skills, from other repositories
accessibility
Use when making a web UI conform to WCAG 2.2 Level AA — axe-core or Lighthouse a11y violations, keyboard operability, focus management, ARIA roles/names/live regions, contrast, tap-target size. NOT palette or visual intent (that is design), NOT test-runner setup (that is testing-web), NOT LCP/page-speed (that is…
accessibility-expert
Build interfaces usable by everyone: WCAG 2.2 conformance, semantic HTML, ARIA, keyboard navigation, screen readers and accessible forms. Use when the user mentions accessibility, a11y, WCAG, ARIA, screen readers, keyboard navigation, colour contrast, focus management, the European Accessibility Act or Section 508, or…
accessibility-engineer
You are the Accessibility Engineering Specialist. You ensure digital products are usable by everyone, including people with visual, auditory, motor, and cognitive disabilities. You audit against WCAG 2.2 standards (AA minimum, AAA preferred), implement ARIA patterns, ensure keyboard navigability, test with screen…
wcag-accessibility
Apply and audit WCAG 2.2 accessibility standards when building or testing frontend components. ALWAYS use this skill when: building any UI component, page, or layout (even if the user doesn't mention accessibility); running accessibility audits or tests; asked to "check a11y", "test accessibility", "audit WCAG…
cognitive-neurodivergent-experience
Guides understanding of how cognitive disabilities and neurodivergence affect web interaction — why timeouts cause panic, why unpredictability causes distress, why sensory overload is pain not preference. Complements the technical patterns in cognitive-a11y with the human WHY. Auto-invokes when creating animations…
disability-user-stories
Generates accessibility-centered user stories, personas, and acceptance criteria that verify real assistive technology experiences. Use when writing user stories, sprint planning, defining acceptance criteria, or creating accessibility-specific test cases. Provides W3C, GOV.UK, and Microsoft persona frameworks plus…