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 iamcxa/kc-claude-pluginsnpx agentmods add plugins/iamcxa/kc-claude-plugins/e2e-pipelinegit clone --depth 1 https://github.com/iamcxa/kc-claude-pluginsWrote 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/iamcxa/kc-claude-plugins/e2e-pipeline)<a href="https://agentmods.dev/plugins/iamcxa/kc-claude-plugins/e2e-pipeline"><img src="https://agentmods.dev/badge/plugins/iamcxa/kc-claude-plugins/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 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
{
"name": "e2e-pipeline",
"description": "Browser & CLI E2E testing pipeline with context-isolating subagents — map UI, generate flows, verify & test, walk through apps, record video, terminal recording for CLI-only flows, static UI computed-style verification",
"version": "3.3.5",
"author": {
"name": "Kent Chen",
"url": "https://github.com/iamcxa"
},
"homepage": "https://github.com/iamcxa/claude-e2e-pipeline",
"repository": "https://github.com/iamcxa/claude-e2e-pipeline",
"license": "MIT",
"keywords": [
"e2e",
"browser-testing",
"agent-browser",
"ui-mapping",
"ui-verify",
"flow-generation",
"flow-verification",
"video-recording",
"cli-recording",
"subagents"
]
}
What it installs
The manifest is a name and a version. 11 skills, 8 agents, 2 hooks travel with it, and installing the plugin installs all of them — 922 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill e2e-flow A 68 tokens
- Skill e2e-debug A 48 tokens
- Skill e2e-walkthrough A 54 tokens
- Skill e2e-map A 45 tokens
- Skill e2e-dispatch A 59 tokens
- Skill e2e-doc-sync A 54 tokens
- Skill e2e-skill-ops A 60 tokens
- Skill ui-verify A 80 tokens
- Skill e2e-help A 46 tokens
- Skill e2e-test B 53 tokens
- Skill e2e-compile B 39 tokens
- Agent e2e-test-runner A 38 tokens
- Agent e2e-flow-verifier A 41 tokens
- Agent e2e-debug-observe A 44 tokens
- Agent e2e-mapper A 33 tokens
- Agent e2e-flow-writer A 41 tokens
- Agent e2e-media-processor A 50 tokens
- Agent doc-probe A 33 tokens
- Agent e2e-trace-analyzer C 36 tokens
- Hook PostToolUse A not measured
- Hook PreToolUse A not measured
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 Changed 10f86621ef65
- 4d ago First seen · 25 lines scan A 755df5d34e9f
e2e-pipeline is a plugin published in the GitHub repository iamcxa/kc-claude-plugins (3 stars, last pushed today), 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
kernel-sdks
TypeScript and Python SDK skills for building browser automation with Kernel's Typescript and Python SDKs.
realbrowser
Target-first local Chrome/Chromium browser control with signed-in profiles, labeled tabs, and guarded actions.
rad-chrome-extension
MV3 Chrome extension development standards (WXT, React, TypeScript) with two pure-stdlib Python validators that catch what LLM eyeballing misses. Skills cover architecture, MV3 security (CSP, remote code ban, content script isolation), permission minimization and CWS compliance, typed messaging, storage selection…
chrome-multi-instance-warn
An agent driving a browser tends to start a new one rather than use the one already open, and to size its work off the core count. This warns once per session when a tool payload is about to do either. Never blocks.
headless
Headless browser automation for site comparison, E2E testing, and anti-bot-aware web research.
claudeshot
Lightweight screenshot capture for Claude Code. PREFERRED over Playwright for web screenshots - uses headless Chrome directly without MCP overhead. Use /screenshot --web URL for quick page captures instead of Playwright browser tools.