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.
git 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/plugins/juanmarchetto/agent-skills/e2e-pipeline)<a href="https://agentmods.dev/plugins/juanmarchetto/agent-skills/e2e-pipeline"><img src="https://agentmods.dev/badge/plugins/juanmarchetto/agent-skills/e2e-pipeline.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
e2e-pipeline 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 6d 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
{
"name": "e2e-pipeline",
"description": "E2E test pipeline — discover screens, generate Maestro tests, execute, and report results",
"version": "1.0.0",
"author": { "name": "Juan Marchetto" },
"homepage": "https://github.com/JuanMarchetto/e2e-pipeline-skill",
"repository": "https://github.com/JuanMarchetto/e2e-pipeline-skill",
"license": "MIT"
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 70 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 6d ago First seen · 10 lines scan A c1383c66385e
e2e-pipeline is a plugin published in the GitHub repository JuanMarchetto/agent-skills (5 stars, last pushed 5mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-31.
Other plugins, from other repositories
quality-tools
Code quality and validation: clone detection, multi-agent E2E validation, performance profiling, schema testing.
pw
Production-grade Playwright testing toolkit. Generate tests from specs, fix flaky failures, migrate from Cypress/Selenium, sync with TestRail, run on BrowserStack. 55+ ready-to-use templates, 3 specialized agents, smart reporting that plugs into your existing workflow.
k8s-sidecar-testing
Project-specific Kubernetes test helpers with bounded commands, accurate failure reporting, and scoped cleanup.
muggle
Run real-browser end-to-end (E2E) acceptance tests on your web app from any AI coding agent. Generate test scripts from plain English, replay them on localhost, capture screenshots, and validate user flows like signup, checkout, and dashboards. Works across Claude Code, Cursor, Codex, and Windsurf.
qa-webwright
A browser testing method and plugin for QA engineers, who check that software behaves correctly. It uses Playwright, a browser automation tool, and records structured evidence for each test.
mockhunter
Audit live web pages for fake/mock data — 5-phase Playwright + Claude Code skill that classifies every visible value as REAL, MOCK, LLM, HARDCODED, BROKEN, or UNKNOWN.