Repository navigation
Standards
github-actions[bot] edited this page Oct 29, 2026
·
3 revisions
One page per standard this package conforms to. Each page states the version relied on, the clauses that matter to this package, how conformance is checked rather than asserted, and any deviation, plainly.
| Standard | Governs here | Checked by |
|---|---|---|
| Agent Skills | every file under skills/
|
skills-ref validate (npm port of the reference validator), npm run verify:spec
|
| AGENTS.md | the always-on contract | size and content, npm run verify:skills
|
| Agent Plugins 1.0 |
plugin.json, mcp.json and the client manifests |
claude plugin validate ., npm run verify:release
|
| Model Context Protocol | the 39 scanner tools | a real client over stdio, npm run verify:mcp
|
| WCAG 2.2 | every criterion a finding cites | npm run verify:findings |
| Hooks, by client | the enforcement gate | 51 tests, node --test hooks/guard.test.mjs
|
| Dependency supply chain | the two dependency trees, root tooling and the MCP server, both gated | the npm advisory database, npm run verify:deps
|
| Open Source Accessibility Framework | the four osaf-* phase skills and their reference skill |
npm run verify:skills for structure; the requirements are pinned to a framework commit and a bundle digest per phase |
The conformance dossier collects the gates, the measured results, the defects found on the way, and the live-client evidence.
Two policy pages sit beside the standards: the citation policy every skill follows when it names a criterion, and the research sources the skills were built from.
It has to govern something in the repository, and something in the repository has to check it. A standard we merely admire does not get a page.
- Agents Overview
- Accessibility Lead
- Web Accessibility Wizard
- Document Accessibility Wizard
- Markdown Assistant
- Developer Hub
- GitHub Hub