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 JuanMarchetto/agent-skills --skill e2e-pipelinegit clone --depth 1 https://github.com/JuanMarchetto/agent-skillsWrote 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/juanmarchetto/agent-skills/e2e-pipeline)<a href="https://agentmods.dev/skills/juanmarchetto/agent-skills/e2e-pipeline"><img src="https://agentmods.dev/badge/skills/juanmarchetto/agent-skills/e2e-pipeline/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/juanmarchetto/agent-skills/e2e-pipeline"><img src="https://agentmods.dev/badge/skills/juanmarchetto/agent-skills/e2e-pipeline.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.00070 | $0.01526 |
| Opus 5 | $0.00035 | $0.00763 |
| Sonnet 5 | $0.00014 | $0.00305 |
| Haiku 4.5 | $0.00007 | $0.00153 |
Grade C, and why
e2e-pipeline scanned grade C with 2 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 11d 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
- If Maestro is not installed: provide install command (`curl -Ls "https://get.maestro.mobile.dev" | bash`) Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- If Maestro is not installed: provide install command (`curl -Ls "https://get.maestro.mobile.dev" | bash`) How it starts
The opening of the file, as written. The whole thing — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E2E Pipeline
Generate and run comprehensive E2E tests from static analysis of your codebase. Discovers all screens, states, and flows, generates Maestro test flows with real assertions, and reports results.
How This Differs From demo-pipeline
demo-pipeline produces marketing assets (video recordings, screenshots, animated demos). e2e-pipeline produces test results (pass/fail verdicts, regression detection, coverage reports). Same discovery phase, completely different output: demo-pipeline asks "does it look good?" while e2e-pipeline asks "does it work correctly?"
Workflow
Pipeline: DISCOVER > DETECT > GENERATE > EXECUTE > REPORT
Phase 0: DISCOVER — Flow & State Analysis
Analyze the codebase to map all screens, states, flows, and native dependencies.
Step 1: Discover screens Read the file-based routing structure:
find src/app -name "*.tsx" -not -name "_layout.tsx" -not -name "+not-found.tsx" | sort
Step 2: Identify states per screen Search for UI conditionals:
grep -n "loading\|isLogged\|isEmpty\|error\|balance.*>\|\.length.*==.*0" src/app/**/*.tsx
Step 3: Map navigation flows
grep -rn "router\.push\|router\.replace\|href=" src/app/ src/components/
Step 4: Identify native dependencies
grep -rn "expo-camera\|CameraView\|useMobileWallet\|SeedVault" src/
Step 5: Present flow map Present the discovered map and ask:
"I discovered N screens with M states and K flows. Which flows do you want to test? (default: all)"
Phase 1: DETECT — Project Type & State
Detect project type (Expo/React Native/web) and check running state (device/emulator/server).
Phase 2: GENERATE — Create Test Flows
For each selected flow, generate a Maestro test YAML with assertions.
Assertion Reference:
| Assertion | Maestro equivalent | Use when |
|---|---|---|
assert_visible: "Text" |
- assertVisible: "Text" |
Verify element appears on screen |
assert_visible: { id: "elem" } |
- assertVisible: { id: "elem" } |
Verify element by testID |
assert_not_visible: "Text" |
- assertNotVisible: "Text" |
Verify element is gone |
assert_contains: { id: "elem", text: "val" } |
- assertVisible: { id: "elem", text: "val" } |
Verify element has specific text |
assert_enabled: { id: "elem" } |
- assertVisible: { id: "elem", enabled: true } |
Verify element is interactive |
assert_count: { text: "Item", count: 5 } |
- assertVisible: "Item" + repeat logic |
Verify expected number of elements |
assert_text_contains: { id: "elem", text: "partial" } |
- assertVisible: { id: "elem", containsText: "partial" } |
Verify partial text match |
screenshot_on_fail: true |
Maestro auto-captures | Capture state on failure |
What ships with it
6 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.
- 11d ago First seen · 166 lines · 70 tokens per session scan C d090550e18b4
e2e-pipeline is a skill published in the GitHub repository JuanMarchetto/agent-skills (5 stars, last pushed 5mo ago), licensed MIT. It adds 70 tokens to every session and 1,526 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
dogfood
QA testing workflow for CamoFox Browser — systematic testing with console capture, error detection, and Playwright tracing. Use when the user needs to test a web application, perform QA validation, do exploratory testing, or verify web app behavior. Triggers include "test this website", "QA", "dogfood", "exploratory…
multi-agent-e2e-validation
Multi-agent parallel E2E validation for database refactors. TRIGGERS - E2E validation, schema migration testing, database refactor validation.
symmetric-dogfooding
Bidirectional integration validation where two repositories validate each other before release.
schema-e2e-validation
Earthly E2E validation for YAML schema contracts. TRIGGERS - schema validation, YAML schema, schema contracts, regenerate types.
playwright-pro
Production-grade Playwright testing skill for E2E suites, flaky test diagnosis, browser automation, migration from Cypress/Selenium, CI integration, visual checks, and regression validation.
browser-qa-delivery
Validate a Design Studio HTML artifact in the sandbox browser, fix rendering and runtime defects, then deliver exactly the tested file.