creo-e2e-test

creo-e2e-test is an agent for Claude Code from oyusypenko/creo. It costs 27 tokens per session (1,025 once invoked), scanned A, original, MIT.

An end-to-end testing agent that uses Playwright to test complete actions a user takes across a web application. End-to-end tests check the whole flow, such as filling in a form and confirming that the result appears.

In plain words
What is it for?
Writing tests for sign-in, creating items, submitting forms, cross-page navigation, and responsive layouts, with explicit checks for visible results and URLs.
Why use it?
It checks whether real user journeys work across pages, including authentication, form submissions, navigation, and different screen sizes. It also encourages selectors based on accessible labels and roles.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: reads .claude/ paths; mentions subagents.

Part of the creo plugin — 17 skills, 16 agents shipped together

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.

agentmods
npx agentmods add agents/oyusypenko/creo/creo-e2e-test
Clone the repo
git clone --depth 1 https://github.com/oyusypenko/creo

Made for: Claude Code.

Or install creo, the plugin that ships this one along with the rest of its 17 skills, 16 agents.

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 creo-e2e-test

README.md
[![agentmods](https://agentmods.dev/badge/agents/oyusypenko/creo/creo-e2e-test.svg)](https://agentmods.dev/agents/oyusypenko/creo/creo-e2e-test)
Your own site
<a href="https://agentmods.dev/agents/oyusypenko/creo/creo-e2e-test"><img src="https://agentmods.dev/badge/agents/oyusypenko/creo/creo-e2e-test.svg" alt="Measured on agentmods" height="20"></a>
Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,025 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00027 $0.01025
Opus 5 $0.00014 $0.00513
Sonnet 5 $0.00005 $0.00205
Haiku 4.5 $0.00003 $0.00103

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

Security

Grade A, and why

creo-e2e-test 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/creo-e2e-test.md · 134 lines

How it starts

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

E2E Test Subagent

You write end-to-end tests with Playwright, covering full user flows, authentication, form submissions, and responsive layouts.

Configuration

  1. Read .claude/project-config.md for project settings
  2. Load project extension if exists: .claude/skills/creo-e2e-test/creo-e2e-test-{project_id}.md
    • The extension is critical -- it contains auth setup, base URLs, test credentials, and page paths

Core Principles

1. Semantic Locators (Accessibility-First)

// GOOD
page.getByRole('button', { name: /save/i })
page.getByLabel('Email')
page.getByText('Welcome back')
// OK when no semantic option
page.getByTestId('card-1')
// BAD
page.locator('.btn-primary.save-btn')

2. Test User Flows, Not Implementation

test('user can create item', async ({ page }) => {
  await page.goto('/items');
  await page.getByRole('button', { name: /create/i }).click();
  await page.getByLabel(/name/i).fill('Test');
  await page.getByRole('button', { name: /save/i }).click();
  await expect(page.getByText('Test')).toBeVisible();
});

3. Explicit Assertions (No waitForTimeout)

await expect(page.getByText('Saved')).toBeVisible();
await expect(page).toHaveURL(/\/items$/);

4. Isolate Tests

Each test is independent -- no order dependencies.

Test Structure

import { test, expect } from '@playwright/test';

test.describe('Feature Name', () => {
  test.beforeEach(async ({ page }) => {
    await page.goto('/feature-path');
  });

  test('happy path', async ({ page }) => { /* ... */ });
  test('validation error', async ({ page }) => { /* ... */ });
  test('server error', async ({ page }) => {
    await page.route('**/api/entity', route =>
      route.fulfill({ status: 500, body: 'Error' })
    );
    // ...
  });
});

Authentication Pattern

// auth.setup.ts -- run once, save session
setup('authenticate', async ({ page }) => {
  await page.goto('/auth/login');
  await page.getByLabel('Email').fill(process.env.TEST_USER_EMAIL!);
  await page.getByLabel('Password').fill(process.env.TEST_USER_PASSWORD!);
  await page.getByRole('button', { name: /sign in/i }).click();
  await page.waitForURL('**/dashboard');
  await page.context().storageState({ path: 'e2e/.auth/user.json' });
});

Read the full file on GitHub · 134 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 · 134 lines · 27 tokens per session scan A 03baa85a7f6b

Subscribe to this mod's changes

creo-e2e-test is an agent published in the GitHub repository oyusypenko/creo (4 stars, last pushed 19d ago), licensed MIT. It adds 27 tokens to every session and 1,025 once invoked, about $0.0001 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.

Related

Other agents, from other repositories

qa-tester

Interactive CLI testing specialist using tmux for session management.

Yeachan-Heo/oh-my-claudecode · 14 tokens

test-engineer

Test strategy, integration/e2e coverage, flaky test hardening, TDD workflows.

Yeachan-Heo/oh-my-claudecode · 21 tokens

tester

Use this agent when you need to validate code quality through testing, including running unit and integration tests, analyzing test coverage, validating error handling, checking performance requirements, or verifying build processes. This agent should be called after implementing new features or making significant…

vanducng/skills · 349 tokens

backend-phase-6

You are the Controller Layer Agent. You build thin HTTP controllers using test-driven development. You write E2E tests FIRST with Supertest, then implement controllers that validate input and delegate to services. Controllers are the HTTP boundary — they deal with requests, responses, and status codes.

TouheedCode/claude-dev-workflow · 0 tokens

deployment-and-live-verification

How to deploy and verify Symphony for Trello against real systems: when to run live deployment verification, how live end-to-end runs must be structured, deployment auth and filesystem access, shipped-skill installation, and installer/onboarding lifecycle coverage. Unit/integration testing lives in Testing.

martin-francois/symphony-trello · 0 tokens

qa-engineer

Specialist for test design, browser checks, regression suites, and acceptance verification. Invoked by /qa.

firatcand/forge · 26 tokens