agentmods.dev

e2e-testing

e2e-testing is a skill for Claude Code from rungchan2/frontend-skills. It costs 147 tokens per session (877 once invoked), scanned A, original, Apache-2.0.

A framework for end-to-end testing from written Markdown scenarios. End-to-end tests check a complete user flow in a real browser, and the framework uses agent-browser to perform the steps, including steps that must wait for a person.

In plain words
What is it for?
Setting up test folders, writing scenarios from the application’s UI, running automatic browser steps, recording human-dependent steps, and saving test results.
Why use it?
It turns test instructions into repeatable browser checks and records steps that cannot be automated, such as payment, CAPTCHA, or one-time codes.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the e2e-testing plugin — 1 skill, 2 commands, 1 agent shipped together

not rated 2repo 4mo ago A scan 147 tokens original Apache-2.0

Good fit Setting up test folders, writing scenarios from the application’s UI, running automatic browser steps, recording human-dependent steps, and saving test results.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/rungchan2/frontend-skills/e2e-testing
View source ↗ rungchan2/frontend-skills
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 rungchan2/frontend-skills --skill e2e-testing
Clone the repo
git clone --depth 1 https://github.com/rungchan2/frontend-skills

Made for: Claude Code.

Or install e2e-testing, the plugin that ships this one along with the rest of its 1 skill, 2 commands, 1 agent.

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 e2e-testing

README.md
[![agentmods](https://agentmods.dev/badge/skills/rungchan2/frontend-skills/e2e-testing.svg)](https://agentmods.dev/skills/rungchan2/frontend-skills/e2e-testing)
Your own site
<a href="https://agentmods.dev/skills/rungchan2/frontend-skills/e2e-testing"><img src="https://agentmods.dev/badge/skills/rungchan2/frontend-skills/e2e-testing.svg" alt="Measured on agentmods" height="20"></a>
Per session 147 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 877 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.00147 $0.00877
Opus 5 $0.00073 $0.00439
Sonnet 5 $0.00029 $0.00175
Haiku 4.5 $0.00015 $0.00088

Measured 8d ago against content hash 5184e0c7e04e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

e2e-testing 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 8d 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.

skills/e2e-testing/skills/e2e-testing/SKILL.md · 83 lines

What it actually says

E2E Testing Framework

마크다운 시나리오 기반 자연어 E2E 테스트. agent-browser CLI + 서브 에이전트 병렬 실행.

요구사항

  • agent-browser CLI 설치 (npm i -g agent-browser)

폴더 구조

.e2e/
├── init.md              # 환경 설정 (Base URL, 로그인 절차) - git 추적 O
├── credentials.md       # 테스트 계정 정보 - git 추적 X (gitignore)
├── results/             # 테스트 결과 - git 추적 X (gitignore)
│   └── {YYYY-MM-DD_HHmm}.md
└── scenarios/
    ├── 1-auth.md
    ├── 2-students.md
    └── ...

시나리오 형식

파일명: {번호}-{기능명}.md

시나리오 파일 형식 상세: references/scenario-format.md 참조.

테스트 스텝 타입

type: auto

에이전트가 agent-browser로 자동 수행. 대부분의 테스트.

type: human

에이전트가 수행 불가한 단계 (결제, CAPTCHA, OTP, 외부 콜백 등). 반드시 유저 행동 필드를 포함. 에이전트는 HUMAN_PENDING 기록 후 다음 auto 스텝 계속 진행.

Setup 워크플로우

"E2E 세팅해줘" 또는 /e2e-testing:setup 시:

  1. .e2e/, .e2e/scenarios/, .e2e/results/ 디렉토리 생성
  2. .e2e/init.md 템플릿 생성 (환경 설정)
  3. .e2e/credentials.md 템플릿 생성 (계정 정보)
  4. .gitignore에 .e2e/credentials.md, .e2e/results/ 추가 확인
  5. 유저에게 credentials.md 직접 채우라고 안내

init.md / credentials.md 템플릿: references/templates.md 참조.

시나리오 작성 워크플로우

"시나리오 만들어줘" 또는 "테스트 케이스 작성" 시:

  1. 기존 시나리오 파일 목록 확인 → 다음 번호 결정
  2. 요청한 기능의 실제 코드를 읽어서 UI 구조 파악
  3. 시나리오 형식에 맞춰 파일 작성

작성 규칙:

  • 1개 파일 = 1개 기능 영역 = 1개 에이전트가 실행
  • 테스트 번호: {시나리오번호}.{테스트번호} (예: 2.1)
  • 모든 스텝에 type 필드 필수
  • human 스텝은 시나리오 후반부에 배치

Run 워크플로우

/e2e-testing:run 시:

  1. .e2e/init.md + .e2e/credentials.md 읽기
  2. 시나리오 선택 (인자 기반)
  3. 각 시나리오마다 e2e-tester 서브 에이전트 병렬 실행
  4. 결과 취합 → .e2e/results/{YYYY-MM-DD_HHmm}.md 단일 파일 저장
Files

What ships with it

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

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. 8d ago First seen · 83 lines · 147 tokens per session scan A 5184e0c7e04e

Subscribe to this mod's changes

e2e-testing is a skill published in the GitHub repository rungchan2/frontend-skills (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 147 tokens to every session and 877 once invoked, about $0.0007 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 skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens