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 paruff/uFawkesAI --skill e2e-test-executiongit clone --depth 1 https://github.com/paruff/uFawkesAIWrote 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/paruff/ufawkesai/e2e-test-execution)<a href="https://agentmods.dev/skills/paruff/ufawkesai/e2e-test-execution"><img src="https://agentmods.dev/badge/skills/paruff/ufawkesai/e2e-test-execution/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/paruff/ufawkesai/e2e-test-execution"><img src="https://agentmods.dev/badge/skills/paruff/ufawkesai/e2e-test-execution.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.00031 | $0.00703 |
| Opus 5 | $0.00015 | $0.00351 |
| Sonnet 5 | $0.00006 | $0.00141 |
| Haiku 4.5 | $0.00003 | $0.00070 |
Grade A, and why
e2e-test-execution 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.
How it starts
The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: End-to-End Test Execution
Load trigger:
"load e2e-test-execution skill"> DORA: Cap 5 (Small Batches / Shift Left on Quality) Token cost: Low
Purpose
Validate full system behavior from the user's perspective.
Responsibilities
- Execute E2E test suite
- Validate workflows end-to-end
- Validate acceptance criteria
- Detect regressions
Inputs
- Build output
- E2E test files
acceptance-criteria.md(or from tasks)
Outputs
e2e-test-results.jsone2e-test-report.md
Execution Rules
Pre-Run
- Application deployed to test environment
- All dependent services running
- Test data seeded
- Browser/UI available (if UI tests)
- API endpoints accessible
Execution
- All E2E workflows executed
- User journeys validated
- Acceptance criteria verified
- Error scenarios validated
Post-Run
- Pass/fail counts recorded
- Failure details captured (with screenshots if UI)
- Acceptance criteria mapping documented
- Regression assessment made
Workflow Validation
User Journey Mapping
| Journey | Test File | Status |
|---|---|---|
| User signup → login → dashboard | signup.e2e.ts |
PASS |
| Create item → edit → delete | crud.e2e.ts |
PASS |
| Checkout flow → payment → confirmation | checkout.e2e.ts |
PASS |
Acceptance Criteria Verification
- Each AC maps to at least one E2E test
- AC test results documented
- Uncovered ACs flagged as findings
Tools
| Type | Tool | Notes |
|---|---|---|
| API | Supertest, httpx, httptest | HTTP-level E2E |
| UI | Playwright, Cypress, Selenium | Browser automation |
| CLI | Bash scripts, expect | Command-line E2E |
Output Format
{
"skill": "e2e-test-execution",
"status": "pass | fail",
"total": 5,
"passed": 5,
"failed": 0,
"workflows_tested": [
"User signup → login → dashboard",
"Create item → edit → delete"
],
"acceptance_criteria_coverage": {
"total": 12,
"covered": 10,
"uncovered": ["AC-11: Multi-language support", "AC-12: Offline mode"]
},
"failures": []
}
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.
- 8d ago First seen · 113 lines · 31 tokens per session scan A 878da7012909
e2e-test-execution is a skill published in the GitHub repository paruff/uFawkesAI (2 stars, last pushed 19d ago), licensed MIT. It adds 31 tokens to every session and 703 once invoked, about $0.0002 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
screen-reader-testing
Test web applications with screen readers including VoiceOver, NVDA, and JAWS. Use when validating screen reader compatibility, debugging accessibility issues, or ensuring assistive technology support.
e2e-testing-patterns
Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.
agent-browser
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
patrol-e2e-testing
Use when writing E2E/integration tests, testing native interactions like permissions or system dialogs, capturing UI regressions, or validating cross-platform behavior (Patrol 4.x).
qa/test-strategy
A testing strategy based on the testing pyramid: many small unit tests, fewer integration tests, and a smaller set of end-to-end tests that follow real user journeys. It also defines checks for security, boundaries, permissions, and business consistency.
e2e-testing
AI-powered E2E testing for any app — Flutter, React Native, iOS, Android, Electron, Tauri, KMP, .NET MAUI. Connects via MCP to running apps so the agent can take screenshots, tap elements, enter text, scroll, inspect UI trees, and verify state with natural language. Use when the user wants to test an app's UI…