cypress

cypress is a skill for Claude Code, Codex from Plazmodium/odin-workflow. It costs 48 tokens per session (2,389 once invoked), scanned A, original, MIT.

Cypress testing guidance for checking web applications in a real browser. It covers end-to-end tests that follow user journeys, component tests, network interception, test data, continuous-integration runs, and browser debugging.

In plain words
What is it for?
Use it to test login and other user journeys, verify components, stub network requests, create fixtures and custom commands, and run tests in CI.
Why use it?
It helps catch failures in complete browser workflows and individual UI components. Its test structure and debugging tools make it easier to reproduce, inspect, and maintain those checks.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to test login and other user journeys, verify components, stub…

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/plazmodium/odin-workflow/cypress
Install

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.

Any agent
npx skills add Plazmodium/odin-workflow --skill cypress
Clone the repo
git clone --depth 1 https://github.com/Plazmodium/odin-workflow

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for cypress

README.md
[![agentmods](https://agentmods.dev/badge/skills/plazmodium/odin-workflow/cypress.svg)](https://agentmods.dev/skills/plazmodium/odin-workflow/cypress)
Your own site
<a href="https://agentmods.dev/skills/plazmodium/odin-workflow/cypress"><img src="https://agentmods.dev/badge/skills/plazmodium/odin-workflow/cypress.svg" alt="Measured on agentmods" height="20"></a>
Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,389 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00048 $0.02389
Opus 5 $0.00024 $0.01195
Sonnet 5 $0.00010 $0.00478
Haiku 4.5 $0.00005 $0.00239

Measured 6d ago against content hash a26c4841637c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

cypress 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.

agents/skills/testing/cypress/SKILL.md · 373 lines

How it starts

The opening of the file, as written. The whole thing — 373 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Cypress End-to-End Testing

Instructions

  1. Assess the testing scope: Determine if it's E2E tests, component tests, or API tests.
  2. Follow Cypress conventions:
    • E2E tests: cypress/e2e/*.cy.ts
    • Component tests: *.cy.tsx alongside components
    • Use cy commands for all interactions
  3. Provide complete examples: Include selectors, assertions, and custom commands.
  4. Guide on best practices: Selectors, waiting, anti-patterns.
  5. Cover advanced features: Intercepts, fixtures, custom commands.

Test Structure

describe('User Authentication', () => {
  beforeEach(() => {
    cy.visit('/login');
  });

  it('should login with valid credentials', () => {
    cy.get('[data-testid="email"]').type('[email protected]');
    cy.get('[data-testid="password"]').type('password123');
    cy.get('[data-testid="submit"]').click();

    cy.url().should('include', '/dashboard');
    cy.get('h1').should('contain', 'Welcome');
  });

  it('should show error for invalid credentials', () => {
    cy.get('[data-testid="email"]').type('[email protected]');
    cy.get('[data-testid="password"]').type('wrong');
    cy.get('[data-testid="submit"]').click();

    cy.contains('Invalid credentials').should('be.visible');
  });
});
// 1. Data attributes (most resilient)
cy.get('[data-testid="submit-button"]');
cy.get('[data-cy="email-input"]');

// 2. Contains text
cy.contains('Submit');
cy.contains('button', 'Submit');  // Element + text

// 3. Role-based (with cypress-testing-library)
cy.findByRole('button', { name: 'Submit' });
cy.findByLabelText('Email');
cy.findByPlaceholderText('Enter email');

// 4. CSS selectors
cy.get('.submit-btn');
cy.get('#email-input');
cy.get('form input[type="email"]');

Common Commands

// Navigation
cy.visit('/page');
cy.go('back');
cy.reload();

// Clicking
cy.get('button').click();
cy.get('button').dblclick();
cy.get('button').rightclick();
cy.get('button').click({ force: true });  // Skip visibility checks

// Typing
cy.get('input').type('Hello');
cy.get('input').type('{enter}');          // Special keys
cy.get('input').type('text{enter}');      // Text + enter
cy.get('input').clear().type('new text');

// Selection
cy.get('select').select('value');
cy.get('select').select(['opt1', 'opt2']); // Multiple

// Checkboxes/Radio
cy.get('input[type="checkbox"]').check();
cy.get('input[type="checkbox"]').uncheck();
cy.get('input[type="radio"]').check('value');

// Focus/Blur
cy.get('input').focus();
cy.get('input').blur();

// Scrolling
cy.scrollTo('bottom');
cy.get('.list').scrollTo(0, 500);

// File upload
cy.get('input[type="file"]').selectFile('path/to/file.pdf');

Read the full file on GitHub · 373 lines

Changes

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.

  1. 6d ago First seen · 373 lines · 48 tokens per session scan A a26c4841637c

Subscribe to this mod's changes

cypress is a skill published in the GitHub repository Plazmodium/odin-workflow (0 stars, last pushed 3mo ago), licensed MIT. It adds 48 tokens to every session and 2,389 once invoked, about $0.0002 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-09-01.

Related

Other skills, from other repositories

orch-e2e

Generate and run end-to-end tests for critical flows.

mattmre/EVOKORE-MCP-PUBLIC · 15 tokens

field-test

Exercise tools, resources, and prompts against a live HTTP server via MCP JSON-RPC over curl. Starts the server, surfaces the catalog, runs real and adversarial inputs, and produces a tight report with concrete findings and numbered follow-up options. Use after adding or modifying definitions, or when the user asks to…

cyanheads/pubmed-mcp-server · 76 tokens

field-test

Exercise tools, resources, and prompts against a live HTTP server via MCP JSON-RPC over curl. Starts the server, surfaces the catalog, runs real and adversarial inputs, and produces a tight report with concrete findings and numbered follow-up options. Use after adding or modifying definitions, or when the user asks to…

cyanheads/oecd-mcp-server · 76 tokens

field-test

Exercise tools, resources, and prompts against a live HTTP server via MCP JSON-RPC over curl. Starts the server, surfaces the catalog, runs real and adversarial inputs, and produces a tight report with concrete findings and numbered follow-up options. Use after adding or modifying definitions, or when the user asks to…

cyanheads/smithsonian-mcp-server · 76 tokens

field-test

Exercise tools, resources, and prompts against a live HTTP server via MCP JSON-RPC over curl. Starts the server, surfaces the catalog, runs real and adversarial inputs, and produces a tight report with concrete findings and numbered follow-up options. Use after adding or modifying definitions, or when the user asks to…

cyanheads/devops-status-mcp-server · 76 tokens

field-test

Exercise tools, resources, and prompts against a live HTTP server via MCP JSON-RPC over curl. Starts the server, surfaces the catalog, runs real and adversarial inputs, and produces a tight report with concrete findings and numbered follow-up options. Use after adding or modifying definitions, or when the user asks to…

cyanheads/osv-advisory-mcp-server · 76 tokens