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 skills add MRCalderon3D/everything-game-dev-code --skill accessibility-designgit clone --depth 1 https://github.com/MRCalderon3D/everything-game-dev-codeWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/mrcalderon3d/everything-game-dev-code/accessibility-design)<a href="https://agentmods.dev/skills/mrcalderon3d/everything-game-dev-code/accessibility-design"><img src="https://agentmods.dev/badge/skills/mrcalderon3d/everything-game-dev-code/accessibility-design/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/mrcalderon3d/everything-game-dev-code/accessibility-design"><img src="https://agentmods.dev/badge/skills/mrcalderon3d/everything-game-dev-code/accessibility-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What 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.1 | $0.00019 | $0.00335 |
| Opus 5 | $0.00010 | $0.00168 |
| Sonnet 5 | $0.00004 | $0.00067 |
| Haiku 4.5 | $0.00002 | $0.00034 |
Grade A, and why
accessibility-design 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 6d 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
Accessibility Design
Purpose
Build accessibility into design decisions instead of treating it as late-stage options work.
Use When
- designing new mechanics, UI, or content
- features rely on reaction speed, color, audio, or precision input
- accessibility scope must be planned
Inputs
- feature spec
- input model
- UI requirements
- audio and narrative needs
Process
- identify likely barriers early
- design equivalent outcomes rather than identical inputs
- specify settings, fallbacks, and persistence behavior
- coordinate with QA and UI for verification
- document limitations explicitly when they cannot be fully solved
Outputs
- accessibility requirements
- option set
- verification targets
- known limitation log
Quality Bar
- supports the core fantasy and player goals
- defines readable rules, edge cases, and feedback
- creates concrete hooks for tuning, telemetry, and QA
Common Failure Modes
- adding systems that do not serve the core loop
- shipping vague rules that QA and engineering must guess at
- tuning without instrumentation or hypotheses
Related Agents
- accessibility-reviewer
- ui-ux-designer
- systems-designer
Related Commands
- verify
- onboarding
- ui-flow-review
Notes
- Keep this skill aligned with the relevant rules layer and current project documentation.
- If engine-specific constraints materially change the workflow, hand off to the matching engine skill or engine-specific reviewer.
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.
- 6d ago First seen · 60 lines · 19 tokens per session scan A af6fb5013946
accessibility-design is a skill published in the GitHub repository MRCalderon3D/everything-game-dev-code (81 stars, last pushed 20d ago), licensed MIT. It adds 19 tokens to every session and 335 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
cgs-design-system
Use for design system tasks that author a system GDD with rules, data, edge cases, progression, feedback, and implementation acceptance tests; produce verification evidence, changed or proposed files, and handoff boundaries.
cgs-prototype
Use for prototype tasks that build or plan a throwaway concept prototype around a falsifiable design hypothesis and cleanup boundary; produce verification evidence, changed or proposed files, and handoff boundaries.
cgs-release-checklist
Use for release checklist tasks that check build, packaging, store, QA, localization, accessibility, rollback, and ship/no-ship readiness; produce verification evidence, changed or proposed files, and handoff boundaries.
cgs-standards-shader-code
Use for shader code standards: review target files, apply Codex-native boundaries, produce violations, fixes, verification evidence, and handoff notes.
cgs-standards-ui
Use for standards ui tasks that hUD, menus, accessibility, localization, controller navigation, and input states; produce verification evidence, changed or proposed files, and handoff boundaries.
cgs-team-ui
Use for team ui tasks that coordinate UI design, implementation, accessibility, localization, controller support, and UX QA; produce verification evidence, changed or proposed files, and handoff boundaries.