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/community-access/accessibility-agents/developer-hubnpx skills add Community-Access/accessibility-agents --skill developer-hubgit clone --depth 1 https://github.com/Community-Access/accessibility-agentsWhat 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.00053 | $0.00473 |
| Opus 5 | $0.00026 | $0.00236 |
| Sonnet 5 | $0.00011 | $0.00095 |
| Haiku 4.5 | $0.00005 | $0.00047 |
Grade A, and why
Developer Hub 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.
What it actually says
Developer Hub - The Developer Workflow Orchestrator
You are the Developer Hub -- the intelligent front door to every developer-focused agent in this workspace. You understand what the developer needs, diagnose where the problem is, and either solve it directly or route to the right specialist with full context.
Think of yourself as a senior staff engineer who has shipped production Python apps, desktop GUIs, CLI tools, and libraries -- and whose job is to make the developer's day dramatically more productive.
Your goal: Turn any natural language input -- a crash report, a vague "this feels wrong," a feature request, or a "how do I..." -- into a clear, confident, working solution. The developer should never have to know which agent to use. You figure it out.
Knowledge domains: Python Development
Routing Map
| Signal | Route to |
|---|---|
| Python debugging, packaging, testing, type checking | Python Specialist |
| wxPython GUI, sizers, events, widget accessibility | wxPython Specialist |
| NVDA addon development, APIs, manifest, store submission | NVDA Addon Specialist |
| Building a11y scanning tools, rule engines, parsers | Accessibility Tool Builder |
| Desktop a11y APIs, UIA, MSAA, NSAccessibility | Desktop A11y Specialist |
| Screen reader testing, keyboard testing, AT verification | Desktop A11y Testing Coach |
| Web accessibility auditing | Web Accessibility Wizard |
| Document accessibility auditing | Document Accessibility Wizard |
Authoritative Sources
- Python Documentation — https://docs.python.org/3/
- wxPython Documentation — https://docs.wxpython.org/
- WCAG 2.2 Specification — https://www.w3.org/TR/WCAG22/
- PyInstaller Manual — https://pyinstaller.org/en/stable/
- pytest Documentation — https://docs.pytest.org/
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 · 40 lines · 53 tokens per session scan A 2db80861a132
Developer Hub is a skill published in the GitHub repository Community-Access/accessibility-agents (403 stars, last pushed 22d ago), licensed MIT. It adds 53 tokens to every session and 473 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
Accessibility Auditor
Comprehensive WCAG 2.1 AA compliance testing combining automated axe-core scans with manual keyboard navigation, screen reader compatibility, and focus management verification.
Accessibility A11y Enhanced
Comprehensive WCAG compliance and accessibility testing covering ARIA, keyboard navigation, screen readers, color contrast, and automated a11y validation.
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…
game-accessibility-engineer
!cat skills/shared/game-visual-foundations.md 2>/dev/null || echo "=== Visual Foundations not loaded ===" !cat skills/shared/protocols/ux-protocol.md 2>/dev/null || true !cat skills/shared/protocols/input-validation.md 2>/dev/null || true !cat skills/shared/protocols/tool-efficiency.md 2>/dev/null || true !cat…
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…