Borrowing it
Nothing to install: this file belongs to cypress-io/cypress-design. 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/cypress-io/cypress-design/main/.agents/skills/cypress-error-messages/SKILL.mdgit clone --depth 1 https://github.com/cypress-io/cypress-designWrote 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/cypress-io/cypress-design/cypress-error-messages)<a href="https://agentmods.dev/skills/cypress-io/cypress-design/cypress-error-messages"><img src="https://agentmods.dev/badge/skills/cypress-io/cypress-design/cypress-error-messages/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/cypress-io/cypress-design/cypress-error-messages"><img src="https://agentmods.dev/badge/skills/cypress-io/cypress-design/cypress-error-messages.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.00118 | $0.01512 |
| Opus 5.5 | $0.00047 | $0.00605 |
| Sonnet 5.5 | $0.00024 | $0.00302 |
| Haiku 4.5 | $0.00012 | $0.00151 |
Grade A, and why
cypress-error-messages 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 2d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cypress Error Message Writer
You help write, review, and improve error messages and warnings for Cypress products. These messages can appear anywhere a developer encounters Cypress: the Cypress App UI, Cypress Cloud, the CLI, and test output. They are often the first signal a developer gets that something is wrong — your job is to make sure they leave that moment with clarity, not confusion.
Before you write
Ask the user for any missing context:
- What happened? What went wrong, failed, or was misconfigured?
- Why did it happen? Is the cause known? Is it user-controlled, a Cypress default, or an environment issue?
- What can the user do next? Is there a fix, a workaround, or a configuration option?
- Is it transient? Will this resolve on its own (e.g., rate limit reset, CI provider issue)?
- Are there interpreted values to show? Did Cypress resolve arguments, flags, or config that the user should see back?
- Is the error being captured by a monitoring system? If yes, and there is no user-actionable fix, the message may include "Our team has been notified." If no, that language must not appear.
- What's the
on.cypress.iolink? See the Links section below.
Do not write the final error message until you have enough information to answer all relevant questions. It's fine to write a draft and flag what's missing.
Error message structure
Every error message should answer these questions in order:
- What happened — in plain terms, no jargon
- Why it happened — if known; skip if genuinely unknown rather than guessing
- What the user should do next — specific steps or options
- What happens if they do nothing — if relevant (e.g., deprecation, data risk)
If the user can't answer "I know what to do next" after reading the message, revise.
Format pattern
[ErrorName or short summary line]
[One to two sentences: what happened and why, if known.]
[If values were interpreted from user input, print them here as a code block so the user can confirm what Cypress resolved.]
[Numbered steps for resolution, if multiple paths exist. Use a single sentence if only one action is needed.]
[Link: https://on.cypress.io/slug]
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.
- 2d ago First seen · 133 lines · 118 tokens per session scan A aac9da2a0dc9
cypress-error-messages is a skill published in the GitHub repository cypress-io/cypress-design (13 stars, last pushed 3d ago), licensed MIT. It adds 118 tokens to every session and 1,512 once invoked, about $0.0005 per session on Opus 5.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-10-28.
Other skills, from other repositories
test-component
Runs, analyzes, and fixes cross-framework interaction, visual-snapshot, aria-snapshot, and accessibility tests for a specific DB UX component's showcase pages.
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…
next-partial-prefetching-optimizer
Optimize what selected Next.js client navigations include before the click under Partial Prefetching. Use after Cache Components and Partial Prefetching are adopted when the user wants selected URL-specific UI to be instant, wants reusable content to wait for navigation, or needs to choose between default, viewport…
vue-component-testing
Applies the three-tier test taxonomy for Vue 3 applications: writes unit tests for composables and Pinia stores with Vitest, component tests for behaviour and user interactions with @testing-library/vue, and acceptance tests for full user flows with Playwright. Ensures tests focus on observable behaviour, not…
sigil-audit
The auditor crawls every /docs/components/ page on the local dev server and combines static MDX analysis with a real Chromium browser pass.
visual-qa
Use when a website needs rendered screenshot review, Playwright visual regression, multi-viewport checks, horizontal overflow detection, console-error checks, focus/state inspection, or a repeatable visual QA evidence set.