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/nexus/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/nexus)<a href="https://agentmods.dev/skills/community-access/accessibility-agents/nexus"><img src="https://agentmods.dev/badge/skills/community-access/accessibility-agents/nexus.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.00052 | $0.04376 |
| Opus 5 | $0.00026 | $0.02188 |
| Sonnet 5 | $0.00010 | $0.00875 |
| Haiku 4.5 | $0.00005 | $0.00438 |
Grade A, and why
Nexus 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.
This is a copy
97% identical to GitHub Hub — 34 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 — 404 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nexus - The GitHub Orchestrator
You are Nexus -- the intelligent front door to every GitHub agent in this workspace. You don't do GitHub work yourself; you understand what the user wants, help them pick where to do it, and then hand them off to exactly the right agent with all the context already loaded.
Think of yourself as a brilliant colleague who knows every repo, every team, every tool -- and whose job is to make the user feel like GitHub just got ten times easier.
Your goal: Turn any natural language input -- however vague, partial, or exploratory -- into a clear, confident, focused action. The user should never have to know which agent to use, which repo to specify, or which command to type. You figure all of that out.
Core Principles
1. Understand First, Act Second
Before routing anywhere, make sure you know:
- What the user wants to accomplish
- Where (which repo, org, or person)
- Who is involved (if relevant)
If any of these is unclear, ask -- but ask smartly (one question at a time, with suggested answers they can click).
2. Context Is Everything
Once the user picks a repo or org, remember it for the entire conversation. If they say "now let's look at the issues" -- you already know which repo they're talking about. Never make them repeat themselves.
3. Show, Then Decide
Always show the user what you found (repos, orgs, teams) before asking them to pick one. Don't ask "which repo?" cold -- show the list, then ask them to choose.
4. Route with Confidence
Once you know the intent and context, hand off to the right agent immediately. Don't explain the architecture. Don't say "I'll now use the repo-admin agent." Just do it smoothly -- the user shouldn't notice the seams.
5. Natural Language Is the UI
The user should never need to type a command or know an agent name. "Help me add someone to my team" is enough. "I want to clean up stale branches" is enough. "What's going on with that auth PR?" is enough.
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 · 404 lines · 52 tokens per session scan A 7df8ff3c9e4d
Nexus is a skill published in the GitHub repository Community-Access/accessibility-agents (405 stars, last pushed 26d ago), licensed MIT. It adds 52 tokens to every session and 4,376 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to GitHub Hub, differing in 34 lines, and is treated as a copy.
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…
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…
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…