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 agents/community-access/accessibility-agents/nexusgit 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.00052 | $0.04820 |
| Opus 5 | $0.00026 | $0.02410 |
| Sonnet 5 | $0.00010 | $0.00964 |
| Haiku 4.5 | $0.00005 | $0.00482 |
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 2d 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
89% identical to github-hub — 46 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 — 436 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Authoritative Sources
- GitHub REST API Documentation — https://docs.github.com/en/rest
- GitHub GraphQL API — https://docs.github.com/en/graphql
- GitHub CLI Manual — https://cli.github.com/manual/
- GitHub Search Syntax — https://docs.github.com/en/search-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.
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.
Platform-Aware Delegation
You are a routing orchestrator. Use the Task tool to delegate work to specialist agents.
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.
- 2d ago First seen · 436 lines · 52 tokens per session scan A 6d93add62e19
nexus is an agent published in the GitHub repository Community-Access/accessibility-agents (403 stars, last pushed 21d ago), licensed MIT. It adds 52 tokens to every session and 4,820 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to github-hub, differing in 46 lines, and is treated as a copy.
Other agents, from other repositories
accessibility-specialist
Accessibility expert: WCAG 2.2 audits, screen reader compat, keyboard navigation, ARIA patterns, automated a11y testing.
ACCESSIBILITY_REVIEWER
You are an elite Digital Accessibility Auditor holding an IAAP CPWA (Certified Professional in Web Accessibility) certification. Your mandate is to evaluate digital interfaces to ensure genuine, human-centered accessibility, prioritizing functional task success and Universal Design over rote technical compliance.
migrate-to-skeleton
Migrates a legacy KoliBri web component to the Skeleton Blueprint architecture (layered controller/FC/props pattern).
a11y-critic
Standalone accessibility design reviewer evaluating ARIA patterns, focus management, state communication, and multi-perspective access (screen reader, keyboard, low vision, cognitive). 8-phase investigation protocol with strict evidence requirements and calibrated severity ratings.
a11y-planner
Accessibility Design Planner — 9-phase protocol for designing accessible implementations before coding. Maps interactive patterns to WAI-ARIA APG patterns, plans focus management, state communication, visual accessibility, content strategy, and testing approach.
bench-runner
Executes a11y skill benchmarks across hosted and local model families. Runs cloud/Codex/Ollama benchmark scripts, monitors progress, handles errors and retries. Reports raw results to the team.