Borrowing it
Nothing to install: this file belongs to open-mercato/cezar. 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/open-mercato/cezar/main/.agents/skills/e2e/SKILL.mdgit clone --depth 1 https://github.com/open-mercato/cezarWrote 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/open-mercato/cezar/e2e)<a href="https://agentmods.dev/skills/open-mercato/cezar/e2e"><img src="https://agentmods.dev/badge/skills/open-mercato/cezar/e2e/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/open-mercato/cezar/e2e"><img src="https://agentmods.dev/badge/skills/open-mercato/cezar/e2e.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.00172 | $0.02402 |
| Opus 5.5 | $0.00069 | $0.00961 |
| Sonnet 5.5 | $0.00034 | $0.00480 |
| Haiku 4.5 | $0.00017 | $0.00240 |
Grade A, and why
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 11d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- e2e — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
e2e: agentic end-to-end tests in TypeScript
e2e runs UI tests with agent goals and exact assertions. agent.act drives
one goal; agent.assert, agent.waitFor, and agent.extract judge the
screen. screen, app, browser, and expect make exact interactions and
checks. The replay cache reruns verified actions and checks their recorded end
state without a model call; agent judgments still run live. UI targets use
@e2e-dev/web for browsers or @e2e-dev/mobile for iOS simulators,
Android emulators, and connected phones. A test that takes only app can check an API with fetch
and expect (topic writing-tests). Model sign-in commands are in
setup.
// e2e.config.ts
import type { E2EConfig } from 'e2e';
import { web } from '@e2e-dev/web';
import { gateway } from 'ai';
export default {
targets: [
{
engine: web(),
app: {
url: 'http://127.0.0.1:3000',
command: { executable: 'pnpm', args: ['dev'], log: '.e2e/logs/app.log' },
},
},
],
// The model behind every agent.* step: an AI SDK instance; gateway() from 'ai' reads AI_GATEWAY_API_KEY or a Vercel OIDC token.
agents: {
default: {
model: gateway('openai/gpt-6-luna-fast'),
system: 'You are a thorough QA agent. Verify every outcome on screen.',
},
},
} satisfies E2EConfig;
// tests/billing.e2e.ts
import { test } from '@e2e-dev/web';
import { expect } from 'e2e';
test('a member upgrades to Pro', async ({ app, agent, screen, browser }) => {
await app.open('/settings/billing');
await agent.act('upgrade the workspace to the Pro plan');
await expect(screen.getByRole('status')).toContainText('Pro');
await expect(browser).toHaveURL('/settings/billing');
});
Topics
Read the topic for the job before writing code. The files sit next to this
one; the installed CLI prints the same text with npx e2e guide <topic>
(e2e guide alone prints this page). For anything the topics do not cover,
the full documentation ships in the docs/ directory of the installed e2e
package (node_modules/e2e/docs in a single-package project); a link such as
/reference/cli is docs/reference/cli.mdx. Complete projects for Vite,
Next.js, Astro, Expo, SwiftUI, Jetpack Compose, Kotlin Multiplatform, and
Flutter, each with its config, scripts, and a passing suite, are in
https://github.com/tester-army/e2e/tree/main/examples.
What ships with it
8 files 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.
- 11d ago First seen · 157 lines · 172 tokens per session scan A 1febf0661e3e
e2e is a skill published in the GitHub repository open-mercato/cezar (776 stars, last pushed today), licensed MIT. It adds 172 tokens to every session and 2,402 once invoked, about $0.0007 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-11.
Other skills, from other repositories
authentication-session-validation
Build repeatable AgentWorks browser validation for authentication and session behavior. Use for login, logout, MFA, recovery, expiry, refresh, and invalid-session coverage after browser setup.
basic-browser-setup
Set up browser QA in AgentWorks, save verified locators and application knowledge, configure a repeatable smoke test, and establish reporting. Use when onboarding an application or repairing its QA foundation.
browser-test-self-healing
Build an AgentWorks workflow that diagnoses a browser-test failure, proposes a test-only repair, verifies it in isolation, obtains the configured review, and updates canonical tests and application knowledge. Use for stale or flaky browser automation, not product defects.
critical-journey-validation
Build AgentWorks browser regression validation using existing application knowledge, test setup, and verified locators. Run approved journeys, investigate failures, and publish durable evidence-backed results.
flaky-test-detection-stabilization
Build AgentWorks browser-test flake detection and reviewed stabilization using repeated isolated attempts and evidence comparison. Use when identical test inputs produce inconsistent outcomes.
release-pr-quality-gate
Build an AgentWorks release or pull-request browser quality gate over saved suites and exact build identity. Use when a merge, deployment, or promotion needs an auditable QA decision.