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 skills add jeremylongworth-source/AgentSkills --skill e2e-test-plangit clone --depth 1 https://github.com/jeremylongworth-source/AgentSkillsWrote 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/jeremylongworth-source/agentskills/e2e-test-plan)<a href="https://agentmods.dev/skills/jeremylongworth-source/agentskills/e2e-test-plan"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/e2e-test-plan/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/jeremylongworth-source/agentskills/e2e-test-plan"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/e2e-test-plan.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.00057 | $0.00312 |
| Opus 5 | $0.00028 | $0.00156 |
| Sonnet 5 | $0.00011 | $0.00062 |
| Haiku 4.5 | $0.00006 | $0.00031 |
Grade A, and why
e2e-test-plan 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 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.
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.
What it actually says
E2E Test Plan
Core Workflow
- Identify the critical user journey, entry point, data setup, success signal, and release risk.
- Choose the smallest E2E path that verifies the user-visible outcome.
- Define setup, actions, assertions, cleanup, test data, and environment.
- Include accessibility, responsive, auth, payment, email, or external-system concerns only when relevant to the journey.
- Separate smoke tests from full regression flows.
- Specify command, CI cadence, flake risks, and manual fallback.
Safety Rules
- Do not use real payment methods, production accounts, or customer data.
- Do not overuse E2E tests for behavior better covered by unit or integration tests.
- Do not claim browser flows work without runtime evidence.
Deliverable Shape
For E2E plans, provide:
- Journey and success criteria
- Environment and test data
- Steps and assertions
- Smoke versus regression scope
- Cleanup
- Command and CI cadence
- Flake risks and mitigations
References
- Read
references/e2e-test-plan-checklist.mdwhen planning E2E coverage.
What ships with it
2 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.
- 7d ago First seen · 42 lines · 57 tokens per session scan A 041390677888
e2e-test-plan is a skill published in the GitHub repository jeremylongworth-source/AgentSkills (1 stars, last pushed 8d ago), licensed MIT. It adds 57 tokens to every session and 312 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-09-03.
Other skills, from other repositories
tester
Run end-to-end web quality audits with Playwright and Lighthouse using existing project scripts first. Use when the user says /tester, e2e test, smoke test, Playwright audit, Lighthouse audit, performance audit, accessibility audit, dark mode audit, mobile audit, or asks for 100/100 Lighthouse improvement guidance.
pptx-html-fidelity-audit
Audit a python-pptx export against its source HTML deck, identify layout/content drift (footer overflow, cropped content, missing italic/em, lost styling, off-rhythm spacing), and re-export with strict footer-rail + cursor-flow layout discipline. Use this skill whenever the user has a .pptx that was generated from an…
jetson-video-pipeline
Use when executing and verifying Jetson Video Codec SDK or PyNvVideoCodec encode/decode, transcode, segmentation, container decode, AV1, or acceptance workflows with exact artifact handoffs.
playwright-skill
Complete browser automation with Playwright. Auto-detects dev servers, writes reusable test scripts, and supports screenshots, responsive checks, UX validation, login flows, link checks, and arbitrary browser automation. Use when the user wants to test a website, automate browser interactions, validate web…
playwright-cli
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…
qa-systematic
Systematic web application QA testing with issue taxonomy, health scoring, and regression tracking. Triggers on: "QA this", "test the app", "smoke test", "run QA", "systematic test", "regression test", "full QA", "/qa-systematic".