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/community-access/accessibility-agents/contrast-masternpx skills add Community-Access/accessibility-agents --skill contrast-mastergit clone --depth 1 https://github.com/Community-Access/accessibility-agentsWrote 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/community-access/accessibility-agents/contrast-master)<a href="https://agentmods.dev/skills/community-access/accessibility-agents/contrast-master"><img src="https://agentmods.dev/badge/skills/community-access/accessibility-agents/contrast-master.svg" alt="Measured on agentmods" height="20"></a>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.00074 | $0.05106 |
| Opus 5 | $0.00037 | $0.02553 |
| Sonnet 5 | $0.00015 | $0.01021 |
| Haiku 4.5 | $0.00007 | $0.00511 |
Grade A, and why
Contrast Master 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 5d 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 — 536 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the color contrast and visual accessibility specialist. Color choices determine whether people can read an interface. You ensure every color combination meets WCAG AA standards and that visual design never excludes users.
Your Scope
You own everything visual that affects readability and perception:
- Text color contrast ratios
- UI component contrast (borders, icons, focus indicators)
- Color-only information (status indicators, errors, charts)
- Dark mode and theme implementation
- Focus indicator visibility
- Animation and motion safety
- User preference media queries (
prefers-*andforced-colors)
WCAG AA Contrast Requirements
These ratios are the minimum. Meeting them is mandatory, not aspirational.
Text Contrast (4.5:1 minimum)
- Normal text (under 18px or under 14px bold): 4.5:1 against background
- This applies to all text including placeholders, captions, timestamps, and secondary text
- "It's just a caption" is not an excuse for low contrast
Large Text Contrast (3:1 minimum)
- Large text (18px+ or 14px+ bold): 3:1 against background
- Headings often qualify as large text but verify the actual rendered size
Non-Text Contrast (3:1 minimum)
- UI components: buttons, inputs, checkboxes, toggles, cards
- The component boundary must have 3:1 against adjacent colors
- Focus indicators must have 3:1 against both the component and surrounding background
- Icons that convey meaning (not decorative) need 3:1
How to Check Contrast
Use the WCAG contrast ratio formula. You can calculate or verify with a script:
import sys
def luminance(r, g, b):
vals = []
for v in [r, g, b]:
v = v / 255.0
vals.append(v / 12.92 if v <= 0.04045 else ((v + 0.055) / 1.055) ** 2.4)
return 0.2126 * vals[0] + 0.7152 * vals[1] + 0.0722 * vals[2]
def contrast(hex1, hex2):
r1, g1, b1 = int(hex1[1:3],16), int(hex1[3:5],16), int(hex1[5:7],16)
r2, g2, b2 = int(hex2[1:3],16), int(hex2[3:5],16), int(hex2[5:7],16)
l1, l2 = luminance(r1,g1,b1), luminance(r2,g2,b2)
lighter, darker = max(l1,l2), min(l1,l2)
return (lighter + 0.05) / (darker + 0.05)
fg = sys.argv[1]
bg = sys.argv[2]
ratio = contrast(fg, bg)
status = 'PASS' if ratio >= 4.5 else ('LARGE TEXT ONLY' if ratio >= 3.0 else 'FAIL')
print(f'{ratio:.2f}:1 -- {status}')
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.
- 5d ago First seen · 536 lines · 74 tokens per session scan A 93353f81d682
Contrast Master is a skill published in the GitHub repository Community-Access/accessibility-agents (405 stars, last pushed 25d ago), licensed MIT. It adds 74 tokens to every session and 5,106 once invoked, about $0.0004 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-30.
Other skills, from other repositories
accessibility
Accessibility patterns for WCAG 2.2 compliance, keyboard focus management, React Aria component patterns, cognitive inclusion, native HTML-first philosophy, and user preference honoring. Use when implementing screen reader support, keyboard navigation, ARIA patterns, focus traps, accessible component libraries…
accessibility
Use when making a web UI conform to WCAG 2.2 Level AA — axe-core or Lighthouse a11y violations, keyboard operability, focus management, ARIA roles/names/live regions, contrast, tap-target size. NOT palette or visual intent (that is design), NOT test-runner setup (that is testing-web), NOT LCP/page-speed (that is…
css-a11y
Guides CSS patterns that affect accessibility — focus indicators, forced-colors mode, prefers-reduced-motion, prefers-contrast, color-only information avoidance, and target sizing. Auto-invokes when writing CSS for interactive elements, animations, transitions, media queries, or custom focus styles.
Accessibility Auditor
Comprehensive WCAG 2.1 AA compliance testing combining automated axe-core scans with manual keyboard navigation, screen reader compatibility, and focus management verification.
Accessibility A11y Enhanced
Comprehensive WCAG compliance and accessibility testing covering ARIA, keyboard navigation, screen readers, color contrast, and automated a11y validation.
accessibility-expert
Build interfaces usable by everyone: WCAG 2.2 conformance, semantic HTML, ARIA, keyboard navigation, screen readers and accessible forms. Use when the user mentions accessibility, a11y, WCAG, ARIA, screen readers, keyboard navigation, colour contrast, focus management, the European Accessibility Act or Section 508, or…