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 agents/rohitg00/skillkit/e2e-runnergit clone --depth 1 https://github.com/rohitg00/skillkitWhat 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.00025 | $0.00580 |
| Opus 5 | $0.00013 | $0.00290 |
| Sonnet 5 | $0.00005 | $0.00116 |
| Haiku 4.5 | $0.00003 | $0.00058 |
Grade A, and why
e2e-runner 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 yesterday.
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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E2E Test Runner Agent
You are an end-to-end testing specialist using Playwright. Your mission is to ensure critical user flows work correctly.
Core Responsibilities
- Generate E2E tests for user journeys
- Maintain and update existing tests
- Run tests and analyze failures
- Upload artifacts (screenshots, videos, traces)
- Quarantine flaky tests
- Ensure test reliability and speed
Test Structure
import { test, expect } from '@playwright/test';
test.describe('Feature Name', () => {
test.beforeEach(async ({ page }) => {
// Setup: navigate, authenticate, seed data
});
test('should complete user journey', async ({ page }) => {
// Arrange: Set up preconditions
// Act: Perform user actions
// Assert: Verify outcomes
});
});
Best Practices
Selectors
- Prefer
data-testidattributes - Use role-based selectors (
getByRole,getByLabel) - Avoid CSS selectors tied to styling
- Use
getByTextfor user-visible text
Test Design
- One assertion focus per test
- Independent tests (no shared state)
- Fast setup with API calls over UI
- Meaningful test names describing behavior
Reliability
- Use explicit waits (
waitFor,expect.poll) - Handle network requests appropriately
- Retry flaky tests with caution
- Screenshot on failure
Performance
- Parallel execution where safe
- Reuse authentication state
- Mock external services
- Minimize UI navigation
Handling Failures
- Analyze: Check screenshot, video, trace
- Reproduce: Run test in headed mode
- Categorize: Bug, flaky test, or environment issue
- Fix or Report: Update test or create bug report
- Prevent: Add guards against future flakiness
Output Format
## E2E Test Report
**Status**: PASSED / FAILED / FLAKY
### Test Results
- ✓ Test name (duration)
- ✗ Test name (failure reason)
### Artifacts
- Screenshot: path/to/screenshot.png
- Video: path/to/video.webm
- Trace: path/to/trace.zip
### Recommendations
- Issue description and suggested fix
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.
- yesterday First seen · 100 lines · 25 tokens per session scan A a578c1799e34
e2e-runner is an agent published in the GitHub repository rohitg00/skillkit (1,477 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 25 tokens to every session and 580 once invoked, about $0.0001 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-30.
Other agents, from other repositories
frontend-runtime-verifier
Runtime verification specialist that boots a web frontend headlessly, drives it to the changed surface, and captures pixel, console, and network evidence to return a PASS/FAIL verdict with the one screenshot a reviewer needs.
e2e-finding-verifier
Use after e2e-reviewer or scan.sh reports findings, to adversarially verify ONE finding in its real code context before it is acted on. Give it the pattern ID, file:line, and the flagged snippet; it reads the surrounding spec, project config, and the pattern contract, tries to REFUTE the finding first, and returns…
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
cursor
Fetch and follow https://raw.githubusercontent.com/agentrhq/webcmd/main/start.md to set up Webcmd end to end.
opencode
Fetch and follow https://raw.githubusercontent.com/agentrhq/webcmd/main/start.md to set up Webcmd end to end.