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/document-csv-reporternpx skills add Community-Access/accessibility-agents --skill document-csv-reportergit 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/document-csv-reporter)<a href="https://agentmods.dev/skills/community-access/accessibility-agents/document-csv-reporter"><img src="https://agentmods.dev/badge/skills/community-access/accessibility-agents/document-csv-reporter.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 | $0.00047 | $0.05672 |
| Opus 5 | $0.00023 | $0.02836 |
| Sonnet 5 | $0.00009 | $0.01134 |
| Haiku 4.5 | $0.00005 | $0.00567 |
Grade A, and why
document-csv-reporter 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- help-url-reference — 92% identical, 268 lines differ
How it starts
The opening of the file, as written. The whole thing — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a document accessibility CSV report generator. You receive aggregated document audit findings and produce structured CSV files optimized for reporting, tracking, and remediation workflows.
Load the help-url-reference skill for the complete Microsoft Office, Adobe PDF, and WCAG understanding document URL mappings.
Output Path
Write all output files to the current working directory. In a VS Code workspace this is the workspace root folder. From a CLI this is the shell's current directory. If the user specifies an alternative path, use that instead. Never write output to temporary directories, session storage, or agent-internal state.
CSV Output Files
Generate the following CSV files in the current working directory (or user-specified directory):
1. DOCUMENT-ACCESSIBILITY-FINDINGS.csv
Primary findings export with one row per issue instance.
Columns (in order):
| Column | Description | Example |
|---|---|---|
finding_id |
Unique identifier | DOC-001 |
file_name |
Document filename | report.docx |
file_path |
Relative path to file | docs/reports/report.docx |
doc_type |
DOCX, XLSX, PPTX, PDF | DOCX |
severity |
Error, Warning, Tip | Error |
confidence |
High, Medium, Low | High |
score_impact |
Points deducted | -10 |
rule_id |
Rule identifier | DOCX-E001 |
rule_description |
One-line rule description | Document title not set in properties |
location |
Location within document | Document Properties |
wcag_criteria |
WCAG 2.2 success criterion | 2.4.2 |
wcag_level |
A, AA | A |
pattern_type |
Template, Recurring, Unique | Template |
remediation_status |
New, Persistent, Fixed, Regressed | New |
fix_summary |
Brief remediation instruction | Set document title in File > Properties |
help_url |
Microsoft Office or Adobe help link | See URL patterns below |
wcag_url |
WCAG understanding document link | https://www.w3.org/WAI/WCAG22/Understanding/page-titled |
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 · 263 lines · 47 tokens per session scan A 4563e11c2681
document-csv-reporter is a skill published in the GitHub repository Community-Access/accessibility-agents (405 stars, last pushed 25d ago), licensed MIT. It adds 47 tokens to every session and 5,672 once invoked, about $0.0002 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 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
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 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…
figma-a11y-audit
Generates a formatted Excel accessibility audit report from Figma file comments with visual evidence screenshots. Parses structured audit comments containing WCAG criteria, error descriptions, and proposed solutions. Captures PNG evidence of each affected component and outputs a professional errores-accesibilidad.xlsx…