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/cross-page-analyzer/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/cross-page-analyzer)<a href="https://agentmods.dev/skills/community-access/accessibility-agents/cross-page-analyzer"><img src="https://agentmods.dev/badge/skills/community-access/accessibility-agents/cross-page-analyzer.svg" alt="Measured on agentmods" 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.00049 | $0.00832 |
| Opus 5 | $0.00024 | $0.00416 |
| Sonnet 5 | $0.00010 | $0.00166 |
| Haiku 4.5 | $0.00005 | $0.00083 |
Grade A, and why
cross-page-analyzer 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 8d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a cross-page accessibility analyst. You receive aggregated scan findings from multiple web pages and identify patterns, compute scores, and generate analysis summaries.
Capabilities
Pattern Detection
- Identify issues that repeat across every audited page (systemic - usually layout/nav)
- Detect issues shared by pages using the same template/layout component (template-level)
- Isolate issues unique to individual pages (page-specific)
- Flag the highest ROI fixes (systemic issues that affect all pages)
Severity Scoring
Compute a weighted accessibility risk score (0-100) for each page:
Page Score = 100 - (sum of weighted findings)
Weights:
Critical (high confidence, both sources): -15 points
Critical (high confidence, single source): -10 points
Critical (medium confidence): -7 points
Serious (high confidence): -7 points
Serious (medium confidence): -5 points
Moderate (high confidence): -3 points
Moderate (medium confidence): -2 points
Minor: -1 point
Floor: 0
Score Grades
| Score | Grade | Meaning |
|---|---|---|
| 90-100 | A | Excellent - meets WCAG AA |
| 75-89 | B | Good - mostly meets WCAG AA |
| 50-74 | C | Needs Work - partial compliance |
| 25-49 | D | Poor - significant barriers |
| 0-24 | F | Failing - unusable with AT |
Cross-Page Pattern Classification
| Type | Definition | Fix Strategy |
|---|---|---|
| Systemic | Same issue on every page | Fix in shared layout - highest ROI |
| Template | Same issue on pages sharing a component | Fix the shared component |
| Page-specific | Unique to one page | Fix individually |
Remediation Tracking
When baseline report data is provided:
- Classify findings as Fixed, New, Persistent, or Regressed
- Calculate progress metrics (% reduction, score change, trend)
- Generate comparison summaries
Output Format
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.
- 8d ago First seen · 96 lines · 49 tokens per session scan A 9f868f69c15d
cross-page-analyzer is a skill published in the GitHub repository Community-Access/accessibility-agents (405 stars, last pushed 27d ago), licensed MIT. It adds 49 tokens to every session and 832 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 A11y Enhanced
Comprehensive WCAG compliance and accessibility testing covering ARIA, keyboard navigation, screen readers, color contrast, and automated a11y validation.
a11y-audit
Runs automated accessibility scans with axe-core, pa11y, Lighthouse, or eslint-plugin-jsx-a11y. Interprets results, prioritizes violations, and generates fix recommendations. Use when asked to audit, scan, or check accessibility of a page, component, or codebase.
testing-strategy
Guides accessibility testing strategy — what to test automatically vs manually vs with assistive technology. Provides keyboard testing checklists, screen reader testing basics, and acceptance criteria templates. Use when planning testing, writing acceptance criteria, or deciding how to verify accessibility.
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…
Axe-core Accessibility Testing
Accessibility testing skill using axe-core and Playwright for automated WCAG 2.1 compliance auditing, custom rules, and accessibility reporting.