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-mapnpx skills add iamcxa/kc-claude-plugins --skill e2e-mapgit 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-map)<a href="https://agentmods.dev/skills/iamcxa/kc-claude-plugins/e2e-map"><img src="https://agentmods.dev/badge/skills/iamcxa/kc-claude-plugins/e2e-map.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.00045 | $0.03825 |
| Opus 5 | $0.00023 | $0.01912 |
| Sonnet 5 | $0.00009 | $0.00765 |
| Haiku 4.5 | $0.00005 | $0.00382 |
Grade A, and why
e2e-map 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 — 310 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E2E Map — Orchestrator
Generate or update the UI element mapping for a web application. Codebase analysis and user interaction run in main context; browser exploration is delegated to the e2e-mapper agent.
Invocation
/e2e-map [--scope page|full] [--page <page-name>] [--interactive]
- No args: full exploration (all pages)
--scope page --page dashboard: re-explore a single page--interactive: skip agent dispatch, run browser exploration inline (for debugging)
--page Mode Behavior
When --page <name> is specified:
- Phase 1: Scope codebase analysis to the target page's route file only
- Phase 2: Agent navigates ONLY to the specified page
- Phase 4: Show unexplored dialogs/modals for THIS page only
- Phase 5: Merge strategy — update only
pages.<name>and any dialogs withtrigger_page: <name>. Preserve all other pages unchanged.
Prerequisites & Pre-Flight
- agent-browser installed globally
If an explicit service manifest is provided or .claude/e2e/services.json
exists, resolve service_runtime to
${CLAUDE_PLUGIN_ROOT}/bin/e2e-local-service-runtime.js, generate one
service_run_id, and use <report_dir>/local-services as the absolute
service_state_dir. Run preflight and start before the first browser
attempt; run stop only after browser handoff/cleanup. The mapper receives
these fields as read-only evidence.
If no mapping exists yet (first map for this app):
- Ask user for
base_url(e.g., "What URL is your dev server running at?") - Ask user for
appname (e.g., "What should I call this app?") - Skip auth — it will be discovered by the mapper agent.
If mapping exists, read base_url and app from it. Capture the file content at this point (store as loaded_mapping_content) — used in Phase 5 for concurrent modification detection.
Resolve ${CLAUDE_PLUGIN_ROOT}/bin/e2e-browser-runtime.js to an absolute
browser_runtime, generate one browser_run_id with node "$browser_runtime" new-run-id, create the absolute report_dir, and set
browser_receipt to <report_dir>/browser-ownership.json. Keep these fields
unchanged for this invocation. Every browser command below uses:
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 · 310 lines · 45 tokens per session scan A 46a292a38593
e2e-map is a skill published in the GitHub repository iamcxa/kc-claude-plugins (3 stars, last pushed yesterday), licensed MIT. It adds 45 tokens to every session and 3,825 once invoked, about $0.0002 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
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
run-integration-tests
Build, pack, and run .NET MAUI integration tests locally. Validates templates, samples, and end-to-end scenarios using the local workload.
cli-e2e-testcase-writer
Use when adding or updating Go CLI E2E coverage for one tests/clie2e/{domain} domain of the compiled lark-cli, especially when the work requires live --help or schema exploration, scenario-based clie2e.RunCmd workflows, and per-domain coverage.md maintenance.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
harness-test-writer
Add regression test cases to the Bifrost provider harness (the Postman collection run via make run-provider-harness-test) based on a merged PR or a GitHub issue. Fetches the PR/issue, traces the affected wire path in the codebase, checks existing harness coverage, designs cases following harness conventions, inserts…
agent-device-evidence
Records iOS/Android native MP4 evidence for test/repro flows extracted from an Expensify GitHub PR or issue. Use when the user asks to "record the flow for PR.