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.
/plugin marketplace add YoungjaeDev/my-claude-pluginsnpx agentmods add plugins/youngjaedev/my-claude-plugins/e2e-harnessgit clone --depth 1 https://github.com/YoungjaeDev/my-claude-pluginsGrade A, and why
e2e-harness 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 2d 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-harness",
"version": "0.2.2",
"description": "Playwright E2E test-harness engineering — wraps Playwright's official AI test agents (npx playwright init-agents --loop=claude generates planner/generator/healer). Three skills close the planner -> generator -> healer self-improving loop: e2e-setup onboards the full harness (agents, auth separation via storageState + setup-project dependency, page.route mocking with Next.js BFF/SSR guidance, E2E operating SSOT doc, GitHub Actions CI with trace/report artifact upload + PR-failure comment + path/label gating); e2e-author selects critical user flows and runs planner -> review-gate -> generator with semantic getByRole locators and a --repeat-each burn-in flake gate; e2e-debug downloads the CI trace, inspects it headlessly, and runs the healer with bounded retries (skip-after-3 + reason comment). Never overwrites an existing playwright.config (merge + backup); degrades gracefully when Playwright is not installed.",
"skills": [
"./skills/e2e-setup",
"./skills/e2e-author",
"./skills/e2e-debug"
]
}
What it installs
The manifest is a name and a version. 3 skills travel with it, and installing the plugin installs all of them — 465 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.
- 2d ago First seen · 11 lines scan A 2bd8e874fefb
e2e-harness is a plugin published in the GitHub repository YoungjaeDev/my-claude-plugins (2 stars, last pushed 7d 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
qa-use
Simplified CLI-integrated plugin for E2E testing with essential slash commands plus dynamic API CLI workflows (qa-use api). Provides AI-first feature verification, browser automation, and test management. All CLI operations documented in SKILL.md and accessible via qa-use docs for harness compatibility.
agent-browser
Automates browser interactions for web testing, form filling, screenshots, and data extraction.
sniff
Autonomous QA scanner via sniff-qa: walks your running app in a real browser and reports real bugs (broken pages/links, console/network errors, broken forms, state-loss, empty/placeholder data, bad loading/error states, responsive + a11y) with reproduction proof, severity, confidence, and a fix. No API key.
headless
Headless browser automation for site comparison, E2E testing, and anti-bot-aware web research.
velocitai
Claude Code 专用 UI 自动化代理治理框架：Playwright + pytest POM 技能、规则和自我进化机制.
uat-agents
User Acceptance Testing workflow for web apps via Chrome DevTools MCP. Includes a setup skill for WSL2, a planning skill with auto-review, a tester skill with resume/abort semantics, and a structured bug-report format that hands off to a debugging agent.