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.
npx agentmods add skills/sjarmak/coding-agent-workflows/e2e-testingnpx skills add sjarmak/coding-agent-workflows --skill e2e-testinggit clone --depth 1 https://github.com/sjarmak/coding-agent-workflowsWhat 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 | $0.00068 | $0.00704 |
| Opus 5 | $0.00034 | $0.00352 |
| Sonnet 5 | $0.00014 | $0.00141 |
| Haiku 4.5 | $0.00007 | $0.00070 |
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 2d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E2E Testing
End-to-end tests are the last line of defense before production: they exercise real user journeys across the whole stack and catch integration failures unit tests structurally cannot. Keep the suite small, critical, and stable — a flaky E2E suite that nobody trusts is worse than none.
Define journeys by risk
Test journeys, not pages. A journey is a full user-visible flow (sign in → create → see it persist). Rank them and cover top-down; do not chase 100% of screens.
- HIGH — money, auth, data loss (payment, login, delete/restore)
- MEDIUM — core navigation, search, primary CRUD
- LOW — cosmetic/UI polish (usually not worth an E2E test)
For each journey cover the happy path first, then the one or two error paths that would actually hurt (declined payment, expired session).
Write for stability
- Semantic locators only.
[data-testid="…"]> role/label > CSS > XPath. A test tied to DOM structure breaks on every refactor; one tied to intent does not. - Wait for conditions, never for time.
waitForResponse()/expect(...).toBeVisible(), neverwaitForTimeout(3000). Time-based waits are the single largest source of flake and they silently slow the suite. - Isolate every test. No shared state, no order dependence; each test sets up and tears down its own data so it can run alone and in parallel.
- Assert at each key step, not just at the end, so a failure points at the step that broke.
Quarantine flake, don't ignore it
A flaky test that stays green-ish erodes trust in the whole suite. When a test flakes:
- Confirm it with a repeat run (
--repeat-each=10or equivalent). - Quarantine it explicitly (
test.fixme/test.skip) with a tracked issue reference in the reason — never a bare skip that disappears silently. - Fix the root cause (usually a time-wait, a race, or shared state), then un-quarantine. Quarantine is a holding cell, not a graveyard.
Capture artifacts on failure
Configure screenshots, video, and traces to record on failure/first-retry (not always — artifacts are expensive). On CI, upload them and put the artifact path in the failure report so a red run is debuggable without a local repro.
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.
- 2d ago First seen · 63 lines · 68 tokens per session scan A 1f1777d151ac
e2e-testing is a skill published in the GitHub repository sjarmak/coding-agent-workflows (2 stars, last pushed 1mo ago), licensed MIT. It adds 68 tokens to every session and 704 once invoked, about $0.0003 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.
Other skills, from other repositories
browser-trace
Capture a full DevTools-protocol trace of any browser automation — CDP firehose, screenshots, and DOM dumps — then bisect the stream into per-page searchable buckets. Use when the user wants to debug a failed run, audit network/console/DOM activity, attach a trace to an in-progress session, or feed structured per-page…
kimi-webbridge
Kimi WebBridge lets AI control the user's real browser — navigate, click, type, read, screenshot, and interact with any website using the user's actual login sessions. Use this skill whenever the user wants to interact with websites, automate browser tasks, scrape web content, or perform any action requiring a real…
opencli-adapter-author
Use when writing an OpenCLI adapter for a new site or adding a new command to an existing site. Guides end-to-end from first recon through field decoding, adapter coding, and verify. Replaces opencli-oneshot / opencli-explorer. For ad-hoc browser driving (no adapter), see opencli-browser instead; for a top-level…
opencli-browser
Use when an agent needs to drive a real Chrome window via opencli — inspect a page, fill forms, click through logged-in flows, or extract data ad-hoc. Covers the selector-first target contract, compound form fields, stale-ref handling, network capture, and the agent-native envelopes the CLI returns. Not for writing…
opencli-usage
Use at the start of any OpenCLI session — this is the top-level map of what opencli can do, how to discover adapters, what flags and output formats are universal, and which specialized skill to load next. Point here when an agent asks "what can opencli do?" or "how do I find the right command?".
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.