Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add iamcxa/kc-claude-plugins/plugin install e2e-pipelineWrote 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/iamcxa/kc-claude-plugins/e2e-walkthrough)<a href="https://agentmods.dev/skills/iamcxa/kc-claude-plugins/e2e-walkthrough"><img src="https://agentmods.dev/badge/skills/iamcxa/kc-claude-plugins/e2e-walkthrough.svg" alt="Measured on agentmods" 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.00054 | $0.05769 |
| Opus 5 | $0.00027 | $0.02884 |
| Sonnet 5 | $0.00011 | $0.01154 |
| Haiku 4.5 | $0.00005 | $0.00577 |
Grade A, and why
e2e-walkthrough scanned grade A with 1 finding 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 7d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -o /dev/null -w "%{http_code}" <base_url> How it starts
The opening of the file, as written. The whole thing — 410 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E2E Walkthrough — Interactive UI Exploration
Human-agent collaborative browser walkthrough with trace recording, health monitoring, and reusable flow output.
Role
Interactive human-in-the-loop browser exploration. Use this when:
- Exploring unknown features — no spec, discovering what the app does
- Visual QA — subjective design review, layout inspection, responsive check
- Debug escape hatch — automated
/e2e-flow --verifyfailed, need human eyes - Demo recording — walkthrough with human narration for stakeholders
For automated flow generation → /e2e-flow
For automated flow verification → /e2e-flow --verify-only
For smoke testing → /e2e-flow --smoke
Pipeline Context
/e2e-map -> mapping.yaml (map)
/e2e-walkthrough -> flow.yaml (explore with human)
/e2e-test -> report.md (replay with monitoring)
Invocation
/e2e-walkthrough [context] [--mode guided|step|auto] [--sites name1,name2] [--pr N] [--issue ID] [--no-video]
| Entry point | Behavior |
|---|---|
--pr 940 |
Read PR diff, propose path covering changed UI |
--issue DRC-2811 |
Read issue, propose path for the feature |
| Free text | Use mapping + codebase to propose path |
--page org-settings |
Explore all mapped elements on that page |
--sites admin,portal |
Cross-site walkthrough using named mappings |
--no-video |
Skip screen recording (default: recording ON) |
Not a walkthrough flag: --verify, --verify-only, --smoke → redirect to /e2e-flow with appropriate flag. Walkthrough is interactive exploration, not automated verification.
Discover Mapping (BLOCKING — must complete before proceeding)
- Look for
.claude/e2e/mappings/*.yaml - One file: use it. Read
app,base_url,authfrom the mapping. - Multiple files: list them (show filename,
app,base_urlfor each), ask user which to use (or accept--mapping <name>). After selection, use ONLY the chosen mapping — do not reference pages/elements from other mapping files. - None: "No mapping files found in
.claude/e2e/mappings/. Mappings define page structure, selectors, and auth config that walkthroughs depend on. Run/e2e-mapto create one first." Stop — do NOT continue to Pre-Flight. "Exploration mode" and "discovery" are NOT reasons to skip mapping — mappings providebase_url,authconfig, and page structure that walkthroughs depend on even for open-ended exploration. - If mapping YAML fails to parse: report the parse error with line number and stop. "Mapping file
<path>has invalid YAML at line N. Fix the syntax error or re-run/e2e-mapto regenerate."
What ships with it
1 file 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.
- 7d ago First seen · 410 lines · 54 tokens per session scan A 14677440c0bc
e2e-walkthrough is a skill published in the GitHub repository iamcxa/kc-claude-plugins (3 stars, last pushed yesterday), licensed MIT. It adds 54 tokens to every session and 5,769 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
browse
Drive a real browser through Aside: open a page, read it, click through a flow, take screenshots, check console errors. (gstack).
playwright-cli
A command-line tool for controlling Chromium, Firefox, and WebKit browsers, including navigation, page interaction, screenshots, PDFs, and recorded actions.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
browser-qa
A browser-based quality check for deployed web pages and user flows. It uses browser automation to test rendering, navigation, forms, interactions, responsive behaviour, and accessibility-related issues.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…
smoke-test
Run smoke tests against a deployed or local app based on your git diff. Each test uses Skyvern browser tools (navigate, act, validate, screenshot) with Chrome DevTools MCP as fallback. Posts screenshot evidence as PR comments.