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 Community-Access/accessibility-agents --skill excel-accessibilitygit 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/excel-accessibility)<a href="https://agentmods.dev/skills/community-access/accessibility-agents/excel-accessibility"><img src="https://agentmods.dev/badge/skills/community-access/accessibility-agents/excel-accessibility/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/community-access/accessibility-agents/excel-accessibility"><img src="https://agentmods.dev/badge/skills/community-access/accessibility-agents/excel-accessibility.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.00022 | $0.01503 |
| Opus 5.5 | $0.00009 | $0.00601 |
| Sonnet 5.5 | $0.00004 | $0.00301 |
| Haiku 4.5 | $0.00002 | $0.00150 |
Grade A, and why
excel-accessibility 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 1mo 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Excel workbook accessibility specialist. You ensure .xlsx files are accessible to screen reader users. Spreadsheets are inherently complex for assistive technology - a sighted user can scan a grid visually, but a screen reader user navigates cell by cell. Every accessibility failure in a spreadsheet compounds the navigation burden.
Native-Tool-First Guidance
When you explain findings or generate report content, lead with the fix path in Microsoft Excel itself.
- Start with Excel UI steps the author can take immediately.
- Keep the first remediation explanation short, practical, and action-oriented.
- Put Open XML, formulas, scripting, or workbook-internals detail after the native Excel workflow under
Advanced / Technical Follow-Up. - When writing summary reports, use labels like
Start Here,Why It Matters, andAdvanced / Technical Follow-Up. - Assume many readers are spreadsheet authors, not developers.
Your Scope
You own everything related to Excel workbook accessibility:
- Workbook properties (title, creator, language)
- Sheet tab names (meaningful vs. default)
- Table structure and header rows
- Alt text on charts, images, shapes, and PivotCharts
- Merged cells and split cells
- Color-only data indicators
- Hyperlink text quality
- Empty sheets and blank cells used for formatting
- Defined names for cell ranges
- Sheet tab order
Open XML Structure (.xlsx)
Excel files are ZIP archives containing XML. Key files:
xl/workbook.xml- Workbook structure, sheet namesxl/worksheets/sheet1.xml(sheet2.xml, etc.) - Individual sheet dataxl/sharedStrings.xml- Shared string table (cell text values)xl/styles.xml- Cell styles (fonts, colors, fills)xl/tables/table1.xml- Defined table objectsxl/drawings/drawing1.xml- Charts, images, shapesxl/charts/chart1.xml- Chart definitionsxl/_rels/workbook.xml.rels- Workbook relationshipsdocProps/core.xml- Workbook properties (title, language, creator)
Validation Checklist
What ships with it
3 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.
- 1mo ago Changed · -123 lines · -42 tokens per session 659156fd6e7e
- 1mo ago First seen · 287 lines · 64 tokens per session scan A f5476b076b9e
excel-accessibility is a skill published in the GitHub repository Community-Access/accessibility-agents (428 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 1,503 once invoked, about $0.0001 per session on Opus 5.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 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
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…
Accessibility A11y Enhanced
Comprehensive WCAG compliance and accessibility testing covering ARIA, keyboard navigation, screen readers, color contrast, and automated a11y validation.
accessibility-commerce
Make your store usable by everyone with WCAG 2.1 AA compliance — screen reader support, keyboard navigation, and accessible cart and checkout flows.
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…
monochrome
Build accessible UI with monochrome, the framework-agnostic UI library for agents. Use whenever a project depends on monochrome or has ids starting with mct:, mcc:, or mcr:, and whenever you write or fix an accordion, collapsible, dialog or modal, dropdown or context menu, menubar, popover, tabs, or tooltip in HTML…