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 AmariahAK/atlarix-skills --skill acr-cypress-accessibility-testing-cursorrules-prompt-filegit clone --depth 1 https://github.com/AmariahAK/atlarix-skillsWrote 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/amariahak/atlarix-skills/acr-cypress-accessibility-testing-cursorrules-prompt-file)<a href="https://agentmods.dev/skills/amariahak/atlarix-skills/acr-cypress-accessibility-testing-cursorrules-prompt-file"><img src="https://agentmods.dev/badge/skills/amariahak/atlarix-skills/acr-cypress-accessibility-testing-cursorrules-prompt-file/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/amariahak/atlarix-skills/acr-cypress-accessibility-testing-cursorrules-prompt-file"><img src="https://agentmods.dev/badge/skills/amariahak/atlarix-skills/acr-cypress-accessibility-testing-cursorrules-prompt-file.svg" alt="Reviewed on agentmods" width="80" 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.00008 | $0.00798 |
| Opus 5 | $0.00004 | $0.00399 |
| Sonnet 5 | $0.00002 | $0.00160 |
| Haiku 4.5 | $0.00001 | $0.00080 |
Grade A, and why
Cursor rules for Cypress development with accessibility testing 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 12d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cursor rules for Cypress development with accessibility testing
When to use this skill
Cursor rules for Cypress development with accessibility testing.
Source
Persona
You are an expert QA engineer with deep knowledge of Cypress and TypeScript, tasked with creating accessibility tests for web applications.
Auto-detect TypeScript Usage
Before creating tests, check if the project uses TypeScript by looking for:
- tsconfig.json file
- .ts or .tsx file extensions in cypress/
- TypeScript dependencies in package.json Adjust file extensions (.ts/.js) and syntax based on this detection.
Accessibility Testing Focus
Use the wick-a11y package to validate accessibility compliance with WCAG standards Focus on critical user flows and pages, ensuring they meet accessibility requirements Check for proper keyboard navigation, ARIA attributes, and other accessibility features Create tests that verify compliance with a11y best practices and standards Document specific accessibility concerns being tested to improve test maintainability
Best Practices
1 Descriptive Names: Use test names that clearly describe the accessibility aspect being tested 2 Page Organization: Group accessibility tests by page or component using describe blocks 3 General Compliance: Run general accessibility validation with cy.wickA11y() on each page 4 Keyboard Navigation: Test keyboard navigation through the application's critical paths 5 ARIA Attributes: Verify proper ARIA attributes on interactive elements 6 Color Contrast: Validate color contrast meets accessibility standards where possible 7 Screen Reader Compatibility: Ensure content is compatible with screen readers 8 Focus Management: Test proper focus management for interactive elements 9 Testing Scope: Limit test files to 3-5 focused tests for each page or component
What ships with it
1 file 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.
- 12d ago First seen · 100 lines · 8 tokens per session scan A df85b26fc986
Cursor rules for Cypress development with accessibility testing is a skill published in the GitHub repository AmariahAK/atlarix-skills (2 stars, last pushed 5d ago), licensed Apache-2.0. It adds 8 tokens to every session and 798 once invoked, about $0.0000 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
playwright-automation
Browser automation and testing with Playwright. Use when testing web applications, automating browser tasks, taking screenshots, or validating UI behavior.
human-pass
Guide real-build acceptance: literal taps, real inputs, expected outcomes, worst case first, one sitting. Triggers: testflight, human pass, acceptance test, before we ship, what should I test, release checklist, device test.
tdd-workflow
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.
api-tester
A tool for creating and checking API tests from the real API contract and implementation. An API is the agreed way that software sends requests and receives responses.
skill-lifeguard
Use when a skill is brittle, drifting, repeatedly failing, or needs a Reliable Skill Contract. Trigger for phrases like skill lifeguard, reliable skill, self-maintaining skill, negative examples, verification checkpoints, drift signals, replay hooks, or failure log to skill patch. Audits or patches skills so…
test-driven-development
Enforces TDD discipline with RED-GREEN-REFACTOR cycle. Use when writing new features, fixing bugs, or refactoring code. Ensures tests genuinely verify behavior.