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 petrkindlmann/qa-skills --skill cypress-automationgit clone --depth 1 https://github.com/petrkindlmann/qa-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/petrkindlmann/qa-skills/cypress-automation)<a href="https://agentmods.dev/skills/petrkindlmann/qa-skills/cypress-automation"><img src="https://agentmods.dev/badge/skills/petrkindlmann/qa-skills/cypress-automation/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/petrkindlmann/qa-skills/cypress-automation"><img src="https://agentmods.dev/badge/skills/petrkindlmann/qa-skills/cypress-automation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk 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.00185 | $0.04226 |
| Opus 5 | $0.00093 | $0.02113 |
| Sonnet 5 | $0.00037 | $0.00845 |
| Haiku 4.5 | $0.00018 | $0.00423 |
Grade A, and why
cypress-automation 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 11d 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 — 271 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quick Route
| You need to... | Go to |
|---|---|
| Write an E2E spec (load, intercept, assert) | Core Principles + references/intercept-patterns.md |
Add a typed custom command / cy.session login |
Custom Commands + references/config-and-commands.md |
| Mount and test a single component | Component Testing + references/component-and-fixtures.md |
Scaffold cypress.config.ts / project layout |
Project Structure + references/config-and-commands.md |
| Stub, spy, simulate errors, or poll an API | cy.intercept Patterns + references/intercept-patterns.md |
| Run in CI / parallelize on Cypress Cloud | CI Integration + references/ci-recipes.md |
| Handle an SSO / OAuth redirect | Cross-Origin Flows + references/intercept-patterns.md |
Discovery Questions
Check .agents/qa-project-context.md first -- if it exists, use it and skip questions already answered there.
- Component testing, E2E, or both? Component testing mounts individual components in isolation; E2E tests the full app through the browser. Most projects need both. Component testing requires a framework-specific mount (React, Vue, Angular, Svelte).
- Cypress Cloud? Cloud provides parallelization, flake detection, analytics, Test Replay, and the AI add-on. If the team uses it, configure
projectIdand the record key. If not, everything runs locally or in CI without Cloud. - TypeScript? Strongly recommended and the default here -- Cypress supports it natively. All examples use TypeScript.
- Framework and bundler? React + Vite, Next.js + Webpack, Vue + Vite, Angular -- component-testing config depends on this.
- Cross-origin auth? If login redirects to a separate domain (SSO, OAuth provider), you need
cy.origin. Note it now so the login command is built for it. - Existing suite or fresh start? If migrating, start with the flakiest or most critical tests, not a big-bang rewrite (see
test-migration).
What ships with it
4 files 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.
- 11d ago First seen · 271 lines · 185 tokens per session scan A ebe5c9195aa8
cypress-automation is a skill published in the GitHub repository petrkindlmann/qa-skills (118 stars, last pushed 3mo ago), licensed MIT. It adds 185 tokens to every session and 4,226 once invoked, about $0.0009 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
Console Error Hunter
Systematically detect, capture, and categorize browser console errors, warnings, and unhandled exceptions during automated test execution.
Geb Testing
Browser automation testing with Geb framework for Groovy/JVM using jQuery-like content DSL, Page Object pattern, Spock integration, and WebDriver abstraction.
playwright-e2e
Comprehensive end-to-end testing skill using Playwright for web applications, covering page objects, selectors, assertions, waits, fixtures, and test organization.
e2e-testing-claude-code
Make Claude Code write and maintain end-to-end tests like a senior SDET — Playwright and Cypress flows with stable locators, the Page Object Model, fixtures, reused auth state, network mocking, and flake-free CI. Claude Code E2E testing, done right.
Browser Agent QA Testing
Teach agents to use AI browser agents for exploratory and smoke QA with step budgets, evidence-based assertions, guardrails, and Playwright conversion.
playwright-execute
Run Playwright tests or suites and upload the resulting report to Katalon True Platform. Use when you need to execute Playwright scripts, package scripts, spec files, projects, or suites, configure or verify @katalon/playwright-reporter, upload Playwright reports with Katalon CLI/reporter commands, and verify uploaded…