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/lfyxhappy/lfcode/e2e-test-engineernpx skills add lfyxhappy/lfcode --skill e2e-test-engineergit clone --depth 1 https://github.com/lfyxhappy/lfcodeWrote 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/lfyxhappy/lfcode/e2e-test-engineer)<a href="https://agentmods.dev/skills/lfyxhappy/lfcode/e2e-test-engineer"><img src="https://agentmods.dev/badge/skills/lfyxhappy/lfcode/e2e-test-engineer.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.00062 | $0.00399 |
| Opus 5 | $0.00031 | $0.00199 |
| Sonnet 5 | $0.00012 | $0.00080 |
| Haiku 4.5 | $0.00006 | $0.00040 |
Grade A, and why
e2e-test-engineer 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 today.
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
End-to-End Test Engineer
Verify a user-visible workflow through the deployed or packaged surface that users actually run.
Workflow
- Read repository instructions, the user journey, acceptance criteria, existing E2E harness, and the actual artifact or service that must be exercised.
- Define the smallest high-risk workflow: entry state, user actions, observable success, recoverable failure, permissions, data ownership, and cleanup.
- Use the repository-approved test environment and automation route. For desktop applications, follow project instructions for packaged or installed-copy validation instead of treating a source-only dev server as release evidence.
- Seed or create isolated data through supported setup paths, then drive the UI or public interface as a user would.
- Assert durable outcomes, visible feedback, navigation, and critical side effects. Prefer semantic locators and explicit readiness signals over layout coordinates and sleeps.
- Capture screenshots, diagnostics, logs, or artifacts only when they help explain a failure. Clean up owned data and rerun the focused workflow before broader release checks.
Boundaries
- Keep workflow analysis and test planning read-only unless the user asks to implement or change E2E tests.
- Do not run destructive flows against production, shared accounts, or user-owned data without explicit authorization.
- Do not replace a product shell, bypass permissions, or rely on source-mode success when the request requires installed-artifact behavior.
- Do not turn a transient timing issue into a permanent arbitrary wait.
Completion Check
Report the user workflow, artifact and environment exercised, setup and cleanup, assertions, diagnostics captured, verification result, and residual platform or external-service risk.
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.
- today First seen · 29 lines · 62 tokens per session scan A bca57e17c0be
e2e-test-engineer is a skill published in the GitHub repository lfyxhappy/lfcode (2 stars, last pushed 3d ago), licensed MIT. It adds 62 tokens to every session and 399 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-05.
Other skills, from other repositories
performance-engineer
Becomes a senior performance engineer who identifies bottlenecks, designs optimization strategies, and conducts load testing using systematic profiling and benchmarking methodology. Use when the user needs performance analysis, load testing, bottleneck identification, latency optimization, or capacity planning. Do NOT…
Review a GitHub PR (via gh)
Review a specific GitHub pull request with gh — fetch the diff, fan out reviewers, consolidate, and optionally post the review. Requires the gh CLI or the GitHub MCP server.
Best of N (parallel attempts)
Delegate N parallel subagents on the same task, then pick the best result.
Design doc (write -> review loop)
Draft a design document and iterate writer/reviewer subagents until consensus.
Implement (multi-agent loop)
Orchestrate an implement -> review -> fix loop with subagents until reviewers sign off.
PR babysit (watch & drive to green)
Watch a pull request and delegate fixes until CI is green and reviews are addressed. Requires the GitHub MCP server or gh.