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/plugin87/full-stack-design-skills/inclusive-design-patternsnpx skills add plugin87/full-stack-design-skills --skill inclusive-design-patternsgit clone --depth 1 https://github.com/plugin87/full-stack-design-skillsWhat 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.00134 | $0.04005 |
| Opus 5 | $0.00067 | $0.02003 |
| Sonnet 5 | $0.00027 | $0.00801 |
| Haiku 4.5 | $0.00013 | $0.00400 |
Grade A, and why
inclusive-design-patterns 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 3d 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 — 668 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Inclusive Design Patterns
Practical patterns for designing interfaces that work for everyone, including people with disabilities.
Accessibility isn't a nice-to-have feature—it's a core design principle. Inclusive design means designing from the start for people with disabilities, rather than retrofitting later. This benefits everyone: captions help in noisy environments, large text helps when tired, and clear navigation helps when distracted.
Core Principle: Design for Constraints
Who Benefits from Accessible Design?
People with permanent disabilities:
- Low vision (reduce text size? Problem. Use zoom + readable fonts.)
- Colorblindness (red/green can't distinguish? Use patterns + labels.)
- Motor impairments (can't use mouse? Keyboard navigation needed.)
- Deaf/hard of hearing (video has no captions? Can't understand.)
- Cognitive differences (complex language? Use clear, simple language.)
People in temporary situations:
- Broken arm (can't use mouse or type)
- Temporary vision loss (bright sun, dark room)
- Noisy environment (can't hear audio)
- Slow internet (images load slowly)
- Interrupted attention (loud office)
People in situational constraints:
- On mobile (small screen, touch, distraction)
- Older adults (presbyopia, tremor, slower reflexes)
- Non-native speakers (complex language is harder)
- Low literacy (jargon and long sentences confusing)
All of the above makes your product better for everyone.
Accessible Color Design
Color Contrast: WCAG Standards
Text must have sufficient contrast to be readable. WCAG defines two levels:
WCAG AA (minimum recommended):
- Regular text (< 18px): 4.5:1 contrast ratio
- Large text (≥ 18px bold or ≥ 24px regular): 3:1 contrast ratio
WCAG AAA (enhanced, for sensitive content):
- Regular text: 7:1 contrast ratio
- Large text: 4.5:1 contrast ratio
Contrast Examples
✅ Good: Black text on white background
- Contrast: 21:1 (very high)
- Passes WCAG AAA
✅ Good: Dark gray (#333) on white
- Contrast: 12.6:1
- Passes WCAG AAA
⚠️ Borderline: Medium gray (#666) on white
- Contrast: 3.3:1
- Fails WCAG AA for regular text
- Passes only for large text (18px+)
❌ Bad: Light gray (#ccc) on white
- Contrast: 1.4:1
- Fails all standards
❌ Bad: Red text on blue background
- Visually colorful but low contrast
- Fails for colorblind users
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 668 lines · 0 tokens per session scan A 4ae23be13bde
inclusive-design-patterns is a skill published in the GitHub repository plugin87/full-stack-design-skills (10 stars, last pushed 1mo ago), licensed MIT. It adds 134 tokens to every session and 4,005 once invoked, about $0.0007 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…