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.
/plugin marketplace add Community-Access/accessibility-agentsnpx agentmods add plugins/community-access/accessibility-agents/marketplacegit clone --depth 1 https://github.com/Community-Access/accessibility-agentsGrade A, and why
community-access 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.
What it actually says
{
"name": "community-access",
"owner": {
"name": "Community Access"
},
"metadata": {
"description": "Accessibility enforcement plugins for Claude Code"
},
"plugins": [
{
"name": "accessibility-agents",
"source": "./claude-code-plugin",
"description": "WCAG AA accessibility enforcement for Claude Code. 80 specialist agents, 25 commands, and enforcement hooks that delegate to accessibility-lead for UI code review. Includes Playwright integration, veraPDF, PDF form converter, end-user documentation, scan config templates, example project, and three-hook enforcement gate.",
"version": "3.2.0",
"author": {
"name": "Taylor Arndt"
},
"category": "accessibility",
"homepage": "https://github.com/Community-Access/accessibility-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 · 23 lines scan A 99be6a456fcc
community-access is a plugin published in the GitHub repository Community-Access/accessibility-agents (403 stars, last pushed 21d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
web-a11y-skills-marketplace
Plugin marketplace listing 1 plugin: a11y.
a11y
Web accessibility skills — semantic markup, ARIA, color contrast, keyboard navigation, screen reader support, testing.
wes-bos-sick-picks
Research-first workflow for building modern, accessible frontend UI components in the spirit of Wes Bos. Researches pitfalls and platform capabilities before planning, designs for WCAG accessibility with modern web standards, then verifies the approach against Wes Bos on X plus trusted sources (MDN, web.dev…
addy-web-quality-skills
Plugin marketplace listing 1 plugin: web-quality-skills.
web-quality-skills
Measurement-first Agent Skills for Lighthouse, Chrome DevTools, Core Web Vitals, WCAG 2.2, SEO, and agentic browsing.
excessibility
LiveView introspection and accessibility testing skills for Phoenix. Use htmlsnapshot() to capture state at any point, axe-core for WCAG compliance, timeline analysis for debugging.