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-helpnpx skills add iamcxa/kc-claude-plugins --skill e2e-helpgit 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-help)<a href="https://agentmods.dev/skills/iamcxa/kc-claude-plugins/e2e-help"><img src="https://agentmods.dev/badge/skills/iamcxa/kc-claude-plugins/e2e-help.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.00046 | $0.01705 |
| Opus 5 | $0.00023 | $0.00852 |
| Sonnet 5 | $0.00009 | $0.00341 |
| Haiku 4.5 | $0.00005 | $0.00170 |
Grade A, and why
e2e-help 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E2E Help -- Interactive Pipeline Guide
Help users discover, understand, and improve the E2E testing pipeline.
Invocation
/e2e-help # Overview of all commands
/e2e-help <topic> # Deep dive into a topic
/e2e-help --feedback "<message>" # Report a doc gap or feature request
/e2e-help --list-topics # Show available help topics
Phase 1 -- Parse Args
| Arg | Mode |
|---|---|
| (none) | Overview (full reference + topics + quick start) |
--list-topics |
Topic list only (lightweight) |
<topic> |
Topic deep dive |
--feedback "<message>" |
Feedback collection |
Phase 2 -- Overview Mode (no args)
Present a complete command reference by reading live skill data:
Read -> ${CLAUDE_PLUGIN_ROOT}/skills/*/SKILL.md (extract name + description from frontmatter)
Read -> ${CLAUDE_PLUGIN_ROOT}/docs/*.md (extract filenames for topic mapping)
IMPORTANT: BOTH tables below (Commands AND Topics) are formatting guides only — populate them from the live reads above. New skills or new doc files added to the plugin MUST appear in the output. Do not emit either template verbatim.
- Commands table: One row per skill. Extract
nameanddescriptionfrom eachskills/*/SKILL.mdfrontmatter. - Topics table: One row per doc file. Derive topic name from filename (strip
.md, use as-is). Read the first heading or first paragraph to generate the "Covers" column. The keyword mapping in Phase 3 provides aliases, but the topic list itself comes from the livedocs/*.mdscan.
Present (format guide — populate from live data):
# E2E Pipeline -- Quick Reference
## Commands
| Command | What it does |
|---------|-------------|
| `/<skill-name>` | <extracted from skill description frontmatter> |
| ... | ... |
## Topics (use `/e2e-help <topic>` for details)
| Topic | Covers |
|-------|--------|
| `<filename-without-extension>` | <derived from doc file first heading or summary> |
| ... | ... |
## Quick Start
**First time?**
1. `/e2e-map` -> map your app
2. `/e2e-flow --smoke` -> generate a smoke test
3. `/e2e-test smoke-navigation` -> run it
**From a plan?**
`/e2e-flow --from plan.md` -> generates + verifies automatically
**Multiple apps?**
`/e2e-test --all-sites` -> runs on every mapped site
**Curated test set?**
`/e2e-test --suite regression` -> runs a defined playlist
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.
- 5d ago First seen · 193 lines · 46 tokens per session scan A 65fc65609088
e2e-help is a skill published in the GitHub repository iamcxa/kc-claude-plugins (3 stars, last pushed today), licensed MIT. It adds 46 tokens to every session and 1,705 once invoked, about $0.0002 per session on Opus 5. 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 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.
__SKILL_ID__
This fixture verifies that skill content can be written into the target sandbox and queried back immediately.
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…