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 dallay/agents-skills --skill cypress-e2egit clone --depth 1 https://github.com/dallay/agents-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/dallay/agents-skills/cypress-e2e)<a href="https://agentmods.dev/skills/dallay/agents-skills/cypress-e2e"><img src="https://agentmods.dev/badge/skills/dallay/agents-skills/cypress-e2e.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.00080 | $0.02074 |
| Opus 5 | $0.00040 | $0.01037 |
| Sonnet 5 | $0.00016 | $0.00415 |
| Haiku 4.5 | $0.00008 | $0.00207 |
Grade A, and why
cypress-e2e 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 6d 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 — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to Use
- Writing end-to-end tests for web applications with Cypress.
- Setting up API mocking with
cy.interceptfor deterministic tests. - Creating reusable custom commands for common workflows.
- Configuring Cypress for CI/CD pipelines.
- Debugging flaky E2E tests or improving test reliability.
Critical Patterns
- Use
data-cyAttributes: NEVER select elements by class name, tag, or content that changes with design or i18n. Use dedicateddata-cyattributes that exist solely for testing. - No Arbitrary Waits: NEVER use
cy.wait(5000). Always wait for specific conditions: route aliases, DOM elements, or assertions that Cypress retries automatically. - Test User Flows, Not Units: E2E tests validate complete workflows (login → navigate → perform action → verify result). For isolated logic, use unit tests.
- API-First Setup: Use
cy.request()or API calls to set up test state (create users, seed data) instead of navigating through the UI. Reserve UI interactions for what you're actually testing. - Each Test Stands Alone: Tests must not depend on previous tests or shared state. Use
beforeEachto set up and clean state for each test.
Code Examples
Test Structure with Selectors
// cypress/e2e/dashboard.cy.ts
describe("Dashboard", () => {
beforeEach(() => {
// Set up state via API — fast and reliable
cy.request("POST", "/api/test/seed", {fixture: "dashboard"});
cy.loginByApi("[email protected]", "password123");
cy.visit("/dashboard");
});
it("displays project list with correct count", () => {
cy.get("[data-cy=project-list]").should("be.visible");
cy.get("[data-cy=project-card]").should("have.length", 3);
});
it("creates a new project", () => {
cy.get("[data-cy=create-project-btn]").click();
cy.get("[data-cy=project-name-input]").type("New Project");
cy.get("[data-cy=project-form-submit]").click();
// Assert on visible result, not internal state
cy.get("[data-cy=project-card]").should("have.length", 4);
cy.contains("[data-cy=project-card]", "New Project").should("exist");
});
it("filters projects by status", () => {
cy.get("[data-cy=filter-dropdown]").click();
cy.get("[data-cy=filter-option-active]").click();
cy.get("[data-cy=project-card]").should("have.length", 2);
cy.get("[data-cy=active-filter-badge]").should("be.visible");
});
});
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.
- 6d ago First seen · 261 lines · 80 tokens per session scan A fb6e8cbf60da
cypress-e2e is a skill published in the GitHub repository dallay/agents-skills (2 stars, last pushed 14d ago), licensed MIT. It adds 80 tokens to every session and 2,074 once invoked, about $0.0004 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…