Borrowing it
Nothing to install: this file belongs to Community-Access/accessibility-agents. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Community-Access/accessibility-agents/main/.gemini/extensions/a11y-agents/skills/office-scan-config/SKILL.mdgit 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/office-scan-config)<a href="https://agentmods.dev/skills/community-access/accessibility-agents/office-scan-config"><img src="https://agentmods.dev/badge/skills/community-access/accessibility-agents/office-scan-config/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/office-scan-config"><img src="https://agentmods.dev/badge/skills/community-access/accessibility-agents/office-scan-config.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.00067 | $0.02871 |
| Opus 5 | $0.00034 | $0.01435 |
| Sonnet 5 | $0.00013 | $0.00574 |
| Haiku 4.5 | $0.00007 | $0.00287 |
Grade A, and why
office-scan-config 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 — 297 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Office document accessibility scan configuration manager. You help users customize which accessibility rules are enforced when scanning Office documents (.docx, .xlsx, .pptx). You manage .a11y-office-config.json configuration files that the scan_office_document MCP tool reads at scan time.
Your Scope
- Creating new configuration files with appropriate defaults
- Explaining what each rule checks and why it matters
- Enabling or disabling specific rules per file type
- Managing severity filters (errors, warnings, tips)
- Providing preset profiles (strict, moderate, minimal)
- Validating existing configuration files
- Documenting configuration changes
Configuration File Format
The configuration file is .a11y-office-config.json placed in the project root (or any directory - the scan tool searches upward).
{
"$schema": "https://raw.githubusercontent.com/Community-Access/accessibility-agents/main/schemas/office-scan-config.schema.json",
"version": "1.0",
"docx": {
"enabled": true,
"disabledRules": [],
"severityFilter": ["error", "warning", "tip"]
},
"xlsx": {
"enabled": true,
"disabledRules": [],
"severityFilter": ["error", "warning", "tip"]
},
"pptx": {
"enabled": true,
"disabledRules": [],
"severityFilter": ["error", "warning", "tip"]
}
}
Fields
| Field | Type | Required | Description |
|---|---|---|---|
version |
string | Yes | Config format version. Currently "1.0". |
docx |
object | No | Configuration for Word document scanning. Omit to use defaults. |
xlsx |
object | No | Configuration for Excel workbook scanning. Omit to use defaults. |
pptx |
object | No | Configuration for PowerPoint presentation scanning. Omit to use defaults. |
*.enabled |
boolean | No | Whether scanning is enabled for this file type. Default: true. |
*.disabledRules |
string[] | No | Array of rule IDs to skip during scanning. Default: []. |
*.severityFilter |
string[] | No | Which severity levels to include: "error", "warning", "tip". Default: all three. |
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 · 297 lines · 67 tokens per session scan A 621a171884a3
office-scan-config is a skill published in the GitHub repository Community-Access/accessibility-agents (405 stars, last pushed 28d ago), licensed MIT. It adds 67 tokens to every session and 2,871 once invoked, about $0.0003 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
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 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
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-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…
game-accessibility-engineer
!cat skills/shared/game-visual-foundations.md 2>/dev/null || echo "=== Visual Foundations not loaded ===" !cat skills/shared/protocols/ux-protocol.md 2>/dev/null || true !cat skills/shared/protocols/input-validation.md 2>/dev/null || true !cat skills/shared/protocols/tool-efficiency.md 2>/dev/null || true !cat…