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 agentmods add skills/iamcxa/kc-claude-plugins/e2e-dispatchnpx skills add iamcxa/kc-claude-plugins --skill e2e-dispatchgit 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/skills/iamcxa/kc-claude-plugins/e2e-dispatch)<a href="https://agentmods.dev/skills/iamcxa/kc-claude-plugins/e2e-dispatch"><img src="https://agentmods.dev/badge/skills/iamcxa/kc-claude-plugins/e2e-dispatch.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 | $0.00059 | $0.02772 |
| Opus 5 | $0.00030 | $0.01386 |
| Sonnet 5 | $0.00012 | $0.00554 |
| Haiku 4.5 | $0.00006 | $0.00277 |
Grade A, and why
e2e-dispatch scanned grade A 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -o /dev/null -w "%{http_code}" <base_url> How it starts
The opening of the file, as written. The whole thing — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E2E Dispatch — Unified Entry Point
Route E2E operations to the correct executor with auth pre-flight.
Invocation
/e2e-dispatch <intent> [options]
| Argument | Example |
|---|---|
--test <flow> |
/e2e-dispatch --test login-flow |
--test --tag <tag> |
/e2e-dispatch --test --tag smoke |
--test --suite <name> |
/e2e-dispatch --test --suite smoke |
--test --all |
/e2e-dispatch --test --all |
--map <app> |
/e2e-dispatch --map my-app |
--map --interactive |
/e2e-dispatch --map my-app --interactive |
--walk [mapping] |
/e2e-dispatch --walk admin-panel |
--flow [--from source] |
/e2e-dispatch --flow --from plan.md |
--flow --smoke |
/e2e-dispatch --flow --smoke |
--flow --verify-only |
/e2e-dispatch --flow --verify-only login-flow |
--analyze <path> |
/e2e-dispatch --analyze .claude/e2e/reports/trace.json |
--compile [flow] |
/e2e-dispatch --compile login-flow |
--compile --all |
/e2e-dispatch --compile --all |
--ops [mode] |
/e2e-dispatch --ops --debug |
No args or ambiguous request: present the routing menu and ask user to choose:
Available E2E operations:
--test— Run E2E test flows (single flow, suite, tag, or all)--map— Create or update UI element mappings--flow— Generate & verify E2E flows from plans/specs/PRs, or smoke test--walk— Interactive walkthrough / explore UI--analyze— Analyze a Playwright ZIP or Chrome Trace JSON artifact--compile— Compile flow YAML to standalone bash test scripts--ops— Debug, maintain, or evaluate E2E skills--help— Interactive help guide & topic deep-dive--doc-sync— Scan docs for gaps, write updates/e2e-debug— Debug frontend runtime bugs (inject logs → browser observe → cleanup) (direct skill — not dispatched, suggest user invoke directly)Which operation? (or describe what you want to do)
Routing priority (when user intent matches multiple routes):
- Explicit
--flag→ use that route directly - Natural language with clear action verb → match: "test/run flow" →
--test, "record/map" →--map, "generate flow/verify flow/smoke test" →--flow, "walk/explore/browse" →--walk, "analyze/trace" →--analyze, "compile/generate script/bash script" →--compile, "fix skill/maintain skill/evaluate skill" →--ops, "help/how/what commands" →--help, "doc/sync docs/update docs" →--doc-sync, "debug runtime/inject logs/browser debug/data shape/why is X empty" → suggest/e2e-debug(direct invocation)
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.
- 4d ago First seen · 200 lines · 59 tokens per session scan A 7892f9043859
e2e-dispatch is a skill published in the GitHub repository iamcxa/kc-claude-plugins (3 stars, last pushed today), licensed MIT. It adds 59 tokens to every session and 2,772 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…