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.
git clone --depth 1 https://github.com/oyusypenko/creoWrote 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/agents/oyusypenko/creo/creo-e2e-test)<a href="https://agentmods.dev/agents/oyusypenko/creo/creo-e2e-test"><img src="https://agentmods.dev/badge/agents/oyusypenko/creo/creo-e2e-test/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/agents/oyusypenko/creo/creo-e2e-test"><img src="https://agentmods.dev/badge/agents/oyusypenko/creo/creo-e2e-test.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.00027 | $0.01025 |
| Opus 5.5 | $0.00011 | $0.00410 |
| Sonnet 5.5 | $0.00005 | $0.00205 |
| Haiku 4.5 | $0.00003 | $0.00103 |
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 1mo 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 — 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
- Read
.claude/project-config.mdfor project settings - 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' });
});
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.
- 1mo ago First seen · 134 lines · 27 tokens per session scan A 03baa85a7f6b
creo-e2e-test is an agent published in the GitHub repository oyusypenko/creo (4 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 1,025 once invoked, about $0.0001 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-08-31.
Other agents, from other repositories
orc-qa-validator
Executor role — drives a real browser via the agent-browser CLI to QA a running web app and writes the evidence packet (criterion screenshots, recording, console, HAR, steps.md, qa-manifest.json) to .orc/ /files/qa/. Dispatched by /orc:qa for web changes.
QA - Test E2E Reviewer
End-to-end browser test gap reviewer that detects webapps, surveys critical user journeys, and recommends gaps or starter strategies. Prescribes Playwright for greenfield. Advisory only.
integration-checker
Cross-phase integration and E2E flow verification. Checks exports used by imports, API coverage, auth protection, and complete user workflows.
e2e-runner
End-to-end testing specialist using Vercel Agent Browser (preferred) with Playwright fallback. Use PROACTIVELY for generating, maintaining, and running E2E tests. Manages test journeys, quarantines flaky tests, uploads artifacts (screenshots, videos, traces), and ensures critical user flows work.
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.
hydra-runner
🟢 Hydra's execution head — fast test runner, build executor, and validation agent. Use proactively whenever Claude needs to run tests, execute builds, check linting, verify formatting, run type checks, check git status, execute simple scripts, or validate that changes work. Runs on the cheap tier for speed — ideal…