OpenClaw Design Audit
openclaw/clawhub
Audits OpenClaw frontend code and rendered pages for token misuse, reimplemented primitives, accessibility and responsive defects and off-brand copy, with an evidence-based report.
Reference data, not a reviewer. An agent skill from Community-Access/accessibility-agents.
Install Kb GitHub A11y Scanner
$ npx skills add Community-Access/accessibility-agents --skill kb-github-a11y-scanner -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Community-Access/accessibility-agents kb-github-a11y-scanner --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/kb-github-a11y-scanner .claude/skills/kb-github-a11y-scanner && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "kb-github-a11y-scanner" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/kb-github-a11y-scanner into .claude/skills/kb-github-a11y-scanner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kb-github-a11y-scanner", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Community-Access/accessibility-agents/tree/main/skills/kb-github-a11y-scannerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Community-Access/accessibility-agents --skill kb-github-a11y-scanner -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Community-Access/accessibility-agents kb-github-a11y-scanner --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/kb-github-a11y-scanner .agents/skills/kb-github-a11y-scanner && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "kb-github-a11y-scanner" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/kb-github-a11y-scanner into .agents/skills/kb-github-a11y-scanner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kb-github-a11y-scanner", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Community-Access/accessibility-agents --skill kb-github-a11y-scanner -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Community-Access/accessibility-agents kb-github-a11y-scanner --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/kb-github-a11y-scanner .cursor/skills/kb-github-a11y-scanner && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "kb-github-a11y-scanner" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/kb-github-a11y-scanner into .cursor/skills/kb-github-a11y-scanner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kb-github-a11y-scanner", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Community-Access/accessibility-agents.git --path skills/kb-github-a11y-scanner--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Community-Access/accessibility-agents --skill kb-github-a11y-scanner -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Community-Access/accessibility-agents kb-github-a11y-scanner --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/kb-github-a11y-scanner .gemini/skills/kb-github-a11y-scanner && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "kb-github-a11y-scanner" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/kb-github-a11y-scanner into .gemini/skills/kb-github-a11y-scanner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kb-github-a11y-scanner", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Community-Access/accessibility-agents kb-github-a11y-scannerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Community-Access/accessibility-agents --skill kb-github-a11y-scanner -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/kb-github-a11y-scanner .github/skills/kb-github-a11y-scanner && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "kb-github-a11y-scanner" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/kb-github-a11y-scanner into .github/skills/kb-github-a11y-scanner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kb-github-a11y-scanner", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Community-Access/accessibility-agents --skill kb-github-a11y-scanner -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Community-Access/accessibility-agents kb-github-a11y-scanner --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/kb-github-a11y-scanner .opencode/skills/kb-github-a11y-scanner && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "kb-github-a11y-scanner" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/kb-github-a11y-scanner into .opencode/skills/kb-github-a11y-scanner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kb-github-a11y-scanner", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
kb-github-a11y-scanner- GitHub stars
- 421
- Token cost
- ~2.4k tokens
- SKILL.md length
- 964 words
- Files
- 2
- Skills in repo
- 108
- Repo updated
- First seen
- Licence
- MIT
At a glance
Reference data, not a reviewer. An agent skill from Community-Access/accessibility-agents.
- Works in 3 steps: Author: The GitHub Actions bot that runs… → Labels: The scanner applies labels to… → Body structure: Issues contain…
- Tasks that involve Accessibility
- SKILL.md covers GitHub Accessibility Scanner…, What Is the GitHub…, Detecting Scanner Presence and Parsing Scanner-Created Issues, plus 5 more sections
- Reaches github.com
What it does
Kb GitHub A11y Scanner is an agent skill from Community-Access/accessibility-agents. Reference data, not a reviewer. Integrate GitHub Accessibility Scanner. Detects configuration, parses scanner issues, correlates with local scans, and tracks Copilot-assigned fixes.
Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It sits in Frontend & Design, covering Accessibility. It works with GitHub. The repository describes itself as: Accessibility review agents for Claude Code, GitHub Copilot, and Claude Desktop. Eleven specialists that enforce WCAG 2.2 AA compliance so AI coding tools stop generating… The licence is MIT.
When your agent uses it
- Tasks that involve Accessibility
Example prompts
- “/kb-github-a11y-scanner”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Author: The GitHub Actions bot that runs the workflow
- Labels: The scanner applies labels to categorize findings (typically accessibility-related labels)
- Body structure: Issues contain structured sections with violation details
What it can do on your machine
Read from SKILL.md and the folder at commit decf6ba. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash, yaml and json).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Kb GitHub A11y Scanner loads about 2.4k tokens when it runs. Until then it costs about 51 tokens; SKILL.md has 964 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Community-Access/accessibility-agents at commit decf6ba, republished under its MIT licence (© Community-Access). 964 words, ~2,397 tokens.
Download SKILL.mdSave it as
.claude/skills/kb-github-a11y-scanner/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- kb-github-a11y-scanner
- description
- Reference data, not a reviewer. Integrate GitHub Accessibility Scanner. Detects configuration, parses scanner issues, correlates with local scans, and tracks Copilot-assigned fixes.
- license
- MIT
- disable-model-invocation
- true
- user-invocable
- false
- metadata.tier
- reference
- metadata.domain
- cross-cutting
- metadata.output
- none
- metadata.effort
- low
- metadata.title
- Github A11y Scanner
GitHub Accessibility Scanner Integration
What Is the GitHub Accessibility Scanner?
The GitHub Accessibility Scanner (github/accessibility-scanner@v2) is an official GitHub Action that:
- Scans live URLs for accessibility barriers using axe-core in a headless browser
- Creates trackable GitHub Issues for each finding, with affected element, WCAG criterion, and remediation guidance
- Optionally assigns issues to GitHub Copilot for AI-powered fix suggestions and PR creation
- Caches results across runs for delta detection (new, fixed, persistent findings)
- Supports authenticated scanning (login flows, SSO, passkeys via Playwright auth context)
- Optionally captures screenshots and attaches them to filed issues
Current version: v2 (public preview)
Detecting Scanner Presence
To determine whether a repository has the GitHub Accessibility Scanner configured:
Workflow File Detection
Search for workflow files referencing the scanner action:
# Search in .github/workflows/ for the scanner action reference
grep -rl "github/accessibility-scanner" .github/workflows/Pattern to match in YAML:
- uses: github/accessibility-scanner@v2Workflow Inputs
When a scanner workflow is found, extract its configuration:
| Input | Required | Description |
|---|---|---|
urls | Yes | Newline-delimited list of URLs to scan |
repository | Yes | Repository (owner/name) where issues and PRs are created |
token | Yes | Fine-grained PAT with write access (contents, issues, PRs, metadata) |
cache_key | Yes | Filename for caching results across runs (e.g., cached_results-mysite.json) |
login_url | No | Login page URL for authenticated scanning |
username | No | Username for authentication |
password | No | Password for authentication (via repository secret) |
auth_context | No | Stringified JSON for complex authentication (Playwright session state) |
skip_copilot_assignment | No | Set true to skip assigning issues to Copilot |
include_screenshots | No | Set true to capture screenshots (stored on gh-cache branch) |
Parsing Scanner-Created Issues
The scanner creates GitHub Issues with a structured format. Agents should parse these fields:
Issue Identification
Scanner-created issues can be identified by:
- Author: The GitHub Actions bot that runs the workflow
- Labels: The scanner applies labels to categorize findings (typically accessibility-related labels)
- Body structure: Issues contain structured sections with violation details
Issue Body Structure
Scanner issues typically contain:
| Section | Content | Agent Use |
|---|---|---|
| Violation title | The axe-core rule that was violated | Map to help-url-reference for remediation docs |
| WCAG criterion | The specific WCAG success criterion | Used for severity scoring and compliance mapping |
| Affected element | CSS selector or HTML snippet of the failing element | Used by scanner-bridge to map to source code |
| Impact level | Critical, Serious, Moderate, or Minor | Direct mapping to agent severity model |
| Remediation guidance | How to fix the issue | Enriched by agent specialists with framework-specific fixes |
| URL | The page URL where the issue was found | Used for cross-referencing with local axe-core scans |
| Screenshot link | Link to screenshot on gh-cache branch (if enabled) | Included in audit reports |
Severity Mapping
The scanner uses axe-core impact levels that map directly to the agent severity model:
| Scanner Impact | Agent Severity | Score Weight |
|---|---|---|
| Critical | Critical | -15 (both sources) / -10 (single source) |
| Serious | Serious | -7 (high confidence) |
| Moderate | Moderate | -3 (high confidence) |
| Minor | Minor | -1 |
axe-core Rule Correlation
The scanner uses axe-core under the hood. Scanner issue titles and violation IDs correspond to axe-core rules already cataloged in help-url-reference. Common scanner-reported rules:
| axe-core Rule ID | WCAG Criterion | Common Description |
|---|---|---|
image-alt | 1.1.1 | Images must have alternate text |
label | 1.3.1 | Form elements must have labels |
color-contrast | 1.4.3 | Elements must have sufficient color contrast |
link-name | 2.4.4 | Links must have discernible text |
html-has-lang | 3.1.1 | <html> element must have a lang attribute |
button-name | 4.1.2 | Buttons must have discernible text |
document-title | 2.4.2 | Documents must have <title> element |
bypass | 2.4.1 | Page must have means to bypass repeated blocks |
heading-order | 1.3.1 | Heading levels should increase by one |
aria-allowed-attr | 4.1.2 | ARIA attributes must be allowed for element role |
Show full SKILL.md (403 more words)Show less
Caching and Delta Detection
The scanner uses a cache_key to persist results across workflow runs. This enables delta tracking:
| Status | Meaning |
|---|---|
| New | Issue found in current scan but not in cached results |
| Fixed | Issue in cached results but not found in current scan (issue auto-closed) |
| Persistent | Issue found in both current scan and cached results |
Cache Key Conventions
When setting up scanner integration, align the cache key with agent conventions:
- Use a descriptive name:
cached_results-{domain}-{branch}.json - Include branch context for branch-specific scanning
- The cache is stored as a GitHub Actions artifact
Correlation with Local Scans
Dual-Source Confidence Boosting
When both the GitHub Accessibility Scanner (CI) and a local axe-core scan (agent) find the same issue:
- Match by rule ID: Both sources use axe-core rule IDs (e.g.,
color-contrast,image-alt) - Match by URL: Compare the scanned URL from the scanner issue with the local scan target
- Match by element: Compare CSS selectors or HTML paths for the affected element
- Boost confidence: Findings confirmed by both sources automatically receive
highconfidence
Source Comparison Analysis
Each scenario, with its interpretation and action.
| Scenario | Interpretation | Action |
|---|---|---|
| Found by scanner AND local scan | High confidence -- confirmed by both | Report as high confidence, full severity weight |
| Found by scanner only | Environment-specific or intermittent | Report as medium confidence, note "CI-only finding" |
| Found by local scan only | New since last CI scan, or local-only condition | Report as medium confidence, note "local-only finding" |
| In scanner cache as "fixed" | Recently remediated | Track in delta section as resolved |
Copilot Fix Tracking
When the scanner assigns issues to GitHub Copilot:
Fix Lifecycle
Each stage, with GitHub state and how to detect.
| Stage | GitHub State | How to Detect |
|---|---|---|
| Issue created | Open issue, assigned to Copilot | assignee includes Copilot bot |
| Fix proposed | Open PR linked to issue | PR references issue number, author is Copilot |
| Fix reviewed | PR has review comments | PR review state is CHANGES_REQUESTED or APPROVED |
| Fix merged | PR merged, issue closed | Issue state is closed, linked PR is merged |
| Fix rejected | PR closed without merge | PR state is closed, not merged |
Querying Copilot Fix Status
# Find scanner issues assigned to Copilot
repo:{REPO} is:issue is:open assignee:copilot label:accessibility
# Find Copilot PRs from scanner issues
repo:{REPO} is:pr author:copilot-swe-agent label:accessibility
# Find merged scanner fixes
repo:{REPO} is:pr is:merged author:copilot-swe-agent label:accessibilityStructured Output Format
When scanner-bridge normalizes scanner issue data, it produces findings in this format:
{
"source": "github-a11y-scanner",
"ruleId": "color-contrast",
"wcagCriterion": "1.4.3",
"wcagLevel": "AA",
"severity": "serious",
"confidence": "high",
"url": "https://example.com/login",
"element": "button.submit-btn",
"description": "Element has insufficient color contrast ratio of 3.2:1 (expected 4.5:1)",
"remediation": "Change the text color or background to achieve at least 4.5:1 contrast ratio",
"githubIssue": {
"number": 42,
"url": "https://github.com/owner/repo/issues/42",
"state": "open",
"copilotAssigned": true,
"fixPR": null
},
"screenshot": "https://github.com/owner/repo/blob/gh-cache/screenshots/login-contrast.png"
}Search Patterns for Scanner Issues
By Repository
repo:{OWNER}/{REPO} is:issue label:accessibility created:>{YYYY-MM-DD}By Scan Run
Issues from a specific scan run share the same creation timestamp and batch pattern. Filter by:
- Creation date matching the workflow run date
- Common label set applied by the scanner
Cross-Repository Scanner Discovery
user:{USERNAME} is:issue label:accessibility sort:created-desc
org:{ORGNAME} is:issue label:accessibility sort:created-desc© Community-Access, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in skills/kb-github-a11y-scanner of Community-Access/accessibility-agents.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit decf6ba
Compare with similar skills
Kb GitHub A11y Scanner next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Kb GitHub A11y Scanner this skillCommunity-Access/accessibility-agents | 421 | — | ~2.4k | Automated safety check: Pass | MIT | |
| OpenClaw Design Auditopenclaw/clawhub | 9.5k | — | ~498 | Automated safety check: Pass | MIT | |
| Web Interface Guidelines Reviewervercel-labs/openreview | 1.7k | 98 repos | ~308 | Automated safety check: Pass | None | |
| Accessibility Reviewmarkmead/hyperui | 12k | 1 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Web Animation DesignbaptisteArno/typebot.io | 11k | 2 repos | ~2.7k | Automated safety check: Pass | Custom licence | |
| Accessibility Fixeribelick/ui-skills | 9.4k | 4 repos | ~1.2k | Automated safety check: Pass | MIT |
Similar skills
- Official
Web Interface Guidelines Reviewer
vercel-labs/openreview
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my…
Accessibility Review
markmead/hyperui
Run a WCAG 2.1 AA accessibility audit on a design or page. An agent skill from markmead/hyperui.
Web Animation Design
baptisteArno/typebot.io
Guides easing, timing and animation choices for UI motion, based on a web animation course, and reviews existing animations in a before-and-after table.
Accessibility Fixer
ibelick/ui-skills
Audits and fixes HTML accessibility problems such as ARIA labels, keyboard navigation, focus management, contrast and form errors with minimal changes.
Wcag Audit Patterns
vmDeshpande/ai-agent-automation
Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance.
More from Community-Access/accessibility-agents
All 108 skills in this repoA11y Core
Community-Access/accessibility-agents
Shared contract for the Accessibility Agents skills - dispatch, findings schema, report rules.
Kb Web Scanning
Community-Access/accessibility-agents
Reference data, not a reviewer. An agent skill from Community-Access/accessibility-agents.
Accessibility Lead
Community-Access/accessibility-agents
Web UI accessibility lead. An agent skill from Community-Access/accessibility-agents.
Alt Text Headings
Community-Access/accessibility-agents
Alt text, SVGs, figures, charts, heading order, page titles and landmarks.
Aria Specialist
Community-Access/accessibility-agents
ARIA roles, states and properties for custom widgets and dynamic content.
Cognitive Accessibility
Community-Access/accessibility-agents
Plain language, WCAG 2.2 cognitive criteria, COGA guidance and auth UX.
Related
Works with
Categories
Questions about Kb GitHub A11y Scanner
What does Kb GitHub A11y Scanner do?
Reference data, not a reviewer. An agent skill from Community-Access/accessibility-agents. Kb GitHub A11y Scanner is an agent skill from Community-Access/accessibility-agents. Reference data, not a reviewer.
When should I use Kb GitHub A11y Scanner?
Kb GitHub A11y Scanner fits situations like: tasks that involve Accessibility.
How do I install Kb GitHub A11y Scanner in Claude Code?
Run `npx skills add Community-Access/accessibility-agents --skill kb-github-a11y-scanner -a claude-code`. Or copy the skill folder (skills/kb-github-a11y-scanner in Community-Access/accessibility-agents) into .claude/skills/kb-github-a11y-scanner in your project. Claude Code loads it when a task matches its description.
How do I install Kb GitHub A11y Scanner in Codex?
Run `npx skills add Community-Access/accessibility-agents --skill kb-github-a11y-scanner -a codex`. Or copy the skill folder (skills/kb-github-a11y-scanner in Community-Access/accessibility-agents) into .agents/skills/kb-github-a11y-scanner in your project. Codex loads it when a task matches its description.
Can I use Kb GitHub A11y Scanner in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Community-Access/accessibility-agents --skill kb-github-a11y-scanner -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/kb-github-a11y-scanner, .gemini/skills/kb-github-a11y-scanner, .github/skills/kb-github-a11y-scanner and .opencode/skills/kb-github-a11y-scanner in your project.
What does Kb GitHub A11y Scanner need to run?
SKILL.md names no scripts, command-line tools or credentials: Kb GitHub A11y Scanner is instructions for the agent only.
Does Kb GitHub A11y Scanner access the network?
SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Kb GitHub A11y Scanner safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Kb GitHub A11y Scanner use?
Kb GitHub A11y Scanner is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Kb GitHub A11y Scanner use?
About 2.4k tokens (SKILL.md is roughly 9.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Kb GitHub A11y Scanner?
Skills that share tags, products or a category with Kb GitHub A11y Scanner: OpenClaw Design Audit (openclaw/clawhub, 9.5k stars), Web Interface Guidelines Reviewer (vercel-labs/openreview, 1.7k stars), Accessibility Review (markmead/hyperui, 12k stars) and Web Animation Design (baptisteArno/typebot.io, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Kb GitHub A11y Scanner?
Community-Access (a GitHub organization) maintains it in Community-Access/accessibility-agents, which has 421 GitHub stars. The repository holds 108 skills in this directory. The repository was last updated on September 23, 2026.
Source: Community-Access/accessibility-agents on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.