Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add iamcxa/kc-claude-plugins/plugin install e2e-pipelineWrote 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/iamcxa/kc-claude-plugins/e2e-compile)<a href="https://agentmods.dev/skills/iamcxa/kc-claude-plugins/e2e-compile"><img src="https://agentmods.dev/badge/skills/iamcxa/kc-claude-plugins/e2e-compile.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.00039 | $0.02627 |
| Opus 5 | $0.00019 | $0.01314 |
| Sonnet 5 | $0.00008 | $0.00525 |
| Haiku 4.5 | $0.00004 | $0.00263 |
Grade B, and why
e2e-compile scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
find ~/.claude/plugins -name "e2e-compile.js" -path "*/e2e-pipeline/bin/*" -print -quit 2>/dev/null How it starts
The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E2E Compile — Flow YAML to Bash Script
Compile E2E flow YAML files into standalone bash test scripts using the e2e-compile CLI.
Invocation
/e2e-compile [flow-name|--all] [--dry-run] [--verbose] [--coverage] [--coverage-output <dir>]
| Arg | Effect |
|---|---|
flow-name |
Compile a single flow (without .yaml extension) |
--all |
Compile every flow in .claude/e2e/flows/ |
--dry-run |
Validate flow + mapping coherence without writing output |
--verbose |
Show resolved step details (operands, expects) during compilation |
--coverage |
Produce static coverage report (elements reached vs verified). Single flow: the data arrives in the JSON document's coverage key. Batch (--all): the batch document has no coverage key, so no coverage data reaches the skill |
--coverage-output <dir> |
Directory for coverage JSON when the compiler is invoked directly. The skill's --json path writes no coverage files, so nothing is written here via /e2e-compile |
Prerequisites
- Flow files in
.claude/e2e/flows/*.yaml— run/e2e-flowor/e2e-walkthroughto create them - Mapping files in
.claude/e2e/mappings/*.yaml— run/e2e-mapfirst if missing
Phase 0 — Parse Arguments
Determine compilation mode from the user's request:
- Explicit flow name → single flow mode
--all→ batch mode (all flows in.claude/e2e/flows/)--dry-run→ validation-only mode (no output file written)--verbose→ add step detail output during compilation (combinable with any mode)
If no flow name and no --all: show help and stop.
Phase 1 — Locate Compiler
Find the e2e-compile.js CLI binary:
- Check
${CLAUDE_PLUGIN_ROOT}/bin/e2e-compile.js(set when plugin is loaded) - If
CLAUDE_PLUGIN_ROOTis not set, search installed locations:
find ~/.claude/plugins -name "e2e-compile.js" -path "*/e2e-pipeline/bin/*" -print -quit 2>/dev/null
If the binary is not found, stop: "Cannot find e2e-compile.js. Ensure the e2e-pipeline plugin is installed."
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 · 150 lines · 39 tokens per session scan B 5a80d9214103
e2e-compile is a skill published in the GitHub repository iamcxa/kc-claude-plugins (3 stars, last pushed yesterday), licensed MIT. It adds 39 tokens to every session and 2,627 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). 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
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…
pyats-dynamic-test
Generate and execute deterministic pyATS aetest validation scripts - interface state, OSPF neighbors, BGP paths, ping matrices, and custom compliance tests. Use when writing a network test, validating post-change state, running pass/fail checks, or building automated regression tests.
trailblaze
Use when working with Trailblaze — natural-language device control for coding agents across iOS, Android, and web, with replayable .trail.yaml files as the artifact. Trigger on mentions of Trailblaze, the trailblaze CLI, .trail.yaml files, trailmaps, waypoints, or requests to drive / author / debug / run UI tests on…
Detox Mobile Testing
Gray-box end-to-end testing for React Native apps with Detox. Covers .detoxrc.js configuration, build and test commands, matchers, device.launchApp control, automatic synchronization, and macOS CI pipelines.