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/redhatinsights/nxtcm-components/e2e-accessibility-analysisnpx skills add RedHatInsights/nxtcm-components --skill e2e-accessibility-analysisgit clone --depth 1 https://github.com/RedHatInsights/nxtcm-componentsWrote 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/redhatinsights/nxtcm-components/e2e-accessibility-analysis)<a href="https://agentmods.dev/skills/redhatinsights/nxtcm-components/e2e-accessibility-analysis"><img src="https://agentmods.dev/badge/skills/redhatinsights/nxtcm-components/e2e-accessibility-analysis.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.00018 | $0.03011 |
| Opus 5 | $0.00009 | $0.01505 |
| Sonnet 5 | $0.00004 | $0.00602 |
| Haiku 4.5 | $0.00002 | $0.00301 |
Grade A, and why
e2e-accessibility-analysis 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 — 371 lines — stays where its author put it; the contents beside it link to each section on GitHub.
e2e-accessibility-analysis
Analyzes E2E Playwright tests to ensure they follow accessibility-first testing patterns using getByRole, getByLabel, and other semantic selectors instead of brittle CSS selectors or test IDs.
When to Use This Skill
- After adding new E2E tests to verify they use accessibility selectors
- Before refactoring E2E tests to improve selector patterns
- When investigating why E2E tests are brittle or breaking frequently
- To audit test quality and adherence to Playwright best practices
- When component accessibility changes may affect test selectors
What This Skill Analyzes
1. Selector Usage Metrics
Counts and categorizes all selectors in E2E tests:
getByRole()- Accessibility-first (BEST)getByLabel()- Accessibility-first (BEST)getByPlaceholder()- Accessibility-first (GOOD)getByText()- Semantic selector (GOOD)getByAltText()- Semantic selector (GOOD)getByTitle()- Semantic selector (GOOD)getByTestId()- Approved fallback when component exposes stable test ID (ACCEPTABLE)locator()with CSS - Last resort only (AVOID)locator()with XPath - Very brittle (AVOID)
2. Accessibility Best Practices
Checks tests for:
- ✅ Human-readable selector names (not IDs, classes, XPath)
- ✅ Semantic HTML roles used for interactions
- ✅ Assertions based on visible text or accessible names
- ✅ Patterns that match how users interact (click buttons, type in textboxes)
- ❌ Brittle selectors tied to implementation (CSS classes, form IDs)
- ❌ Overly-specific selectors requiring DOM structure knowledge
3. Component Accessibility Gaps
Identifies when tests must use fallback selectors (test IDs or CSS) due to missing accessible names:
- Components without proper
aria-labelor visible labels → usedata-testidif provided - Dropdowns/selects without accessible names on toggle buttons → use
data-testidif provided - Custom widgets that don't expose semantic roles → use
data-testidif provided - PatternFly components missing accessibility props → prefer
data-testidover CSS when available
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 · 371 lines · 18 tokens per session scan A fa82e662f56a
e2e-accessibility-analysis is a skill published in the GitHub repository RedHatInsights/nxtcm-components (3 stars, last pushed yesterday), licensed Apache-2.0. It adds 18 tokens to every session and 3,011 once invoked, about $0.0001 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-31.
Other skills, from other repositories
testing-e2e
End-to-end testing patterns with Playwright — page objects, AI agent testing, visual regression, accessibility testing with axe-core, and CI integration. Use when writing E2E tests, setting up Playwright, implementing visual regression, or testing accessibility.
expect
Diff-aware AI browser testing — reads the git diff, maps changes to affected pages via the route map, generates a targeted test plan, and executes it via agent-browser (Rust daemon + CDP, ARIA-tree-first) with pass/fail reporting. Use when testing UI changes, verifying PRs before merge, or running regression checks on…
Axe-core Accessibility Testing
Accessibility testing skill using axe-core and Playwright for automated WCAG 2.1 compliance auditing, custom rules, and accessibility reporting.
e2e-testing
Use when writing or stabilizing Playwright tests that drive a real browser through multi-step journeys — durable locators, web-first assertions, storageState auth, trace/retries, and flakes that only bite in CI. NOT in-process component tests (that is testing-web), NOT WCAG auditing (that is accessibility), NOT the…
hatch3r-browser-verify
Opt-in browser verification skill — spec-run-first Playwright verification (assertions execute in the runner, agent reads only failures), axe-core a11y audits, toHaveScreenshot() regression diffs, E2E test scaffolds, and snapshot-mode exploratory driving. Default ON for UI-affecting agent invocations; disable globally…
e2e-testing
End-to-end testing for Falcon Foundry apps using Playwright and @crowdstrike/foundry-playwright. TRIGGER when user asks to "add e2e tests", "add playwright tests", "write end-to-end tests", "test my app", or mentions "e2e", "playwright", or "end-to-end" in the context of testing a Foundry app. DO NOT TRIGGER during…