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/github-scanningnpx skills add Community-Access/accessibility-agents --skill github-scanninggit 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.00075 | $0.01983 |
| Opus 5 | $0.00037 | $0.00992 |
| Sonnet 5 | $0.00015 | $0.00397 |
| Haiku 4.5 | $0.00007 | $0.00198 |
Grade A, and why
github-scanning 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.
How it starts
The opening of the file, as written. The whole thing — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Scanning
Search Query Patterns by Intent
Issues
| Intent | Query Pattern | Scope |
|---|---|---|
| Assigned to you | is:open assignee:USERNAME |
All repos |
| You were @mentioned | is:open mentions:USERNAME |
All repos |
| Authored by you | is:open author:USERNAME |
All repos |
| Specific repo | repo:owner/repo is:open |
Single repo |
| By keyword | {keyword} is:open |
All repos |
| Org-wide | org:ORGNAME is:open |
Org repos |
| Closed (for recap) | is:closed author:USERNAME |
All repos |
Pull Requests
| Intent | Query Pattern | Scope |
|---|---|---|
| Awaiting your review | review-requested:USERNAME state:open |
All repos |
| Your open PRs | author:USERNAME state:open |
All repos |
| Assigned to you | assignee:USERNAME state:open |
All repos |
| You reviewed, check for updates | reviewed-by:USERNAME state:open |
All repos |
| Specific PR | Fetch directly with owner, repo, number | Single repo |
| Org-wide | org:ORGNAME state:open |
Org repos |
Discussions
| Intent | Action |
|---|---|
| You're mentioned | Search with mentions:USERNAME |
| You're participating | Search discussions you've commented on |
| High activity | Filter for 10+ comments in last 24h |
| Linked to your issues | Scan description/comments for issue references |
Releases
- Use
github_list_releasesper repo - check for recent, draft, and pre-releases. - Cross-reference merged PRs against release notes to identify unreleased work.
- Compare issue milestones against release schedules to flag upcoming deadline items.
Security
- Dependabot alerts: critical and high severity across monitored repos.
- Security advisories affecting dependencies.
- Pending dependency update PRs from
dependabot[bot]orrenovate[bot].
CI/CD
- Fetch recent workflow runs - identify failing workflows, long jobs, and flaky tests.
- For failing workflows: note repo, workflow name, branch, failure reason, and link to run.
- Cross-reference user's open PRs against CI results.
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 · 217 lines · 75 tokens per session scan A 7ec8fecce381
github-scanning is a skill published in the GitHub repository Community-Access/accessibility-agents (403 stars, last pushed 21d ago), licensed MIT. It adds 75 tokens to every session and 1,983 once invoked, about $0.0004 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…