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-flownpx skills add iamcxa/kc-claude-plugins --skill e2e-flowgit 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-flow)<a href="https://agentmods.dev/skills/iamcxa/kc-claude-plugins/e2e-flow"><img src="https://agentmods.dev/badge/skills/iamcxa/kc-claude-plugins/e2e-flow.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.00068 | $0.07505 |
| Opus 5 | $0.00034 | $0.03753 |
| Sonnet 5 | $0.00014 | $0.01501 |
| Haiku 4.5 | $0.00007 | $0.00751 |
Grade A, and why
e2e-flow 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Scan source material (conversation context, `--from` file content) for CLI signals: shell commands (`curl`, `psql`, `npm run`, `bun`, script paths), API endpoint testing, database queries, migration scripts, `Execute e How it starts
The opening of the file, as written. The whole thing — 623 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E2E Flow — Generate & Verify
Generate and verify E2E flows — browser UI, CLI commands, or API checkpoints. Combines autonomous flow generation (codebase analysis, no browser) with adaptive verification: browser flows use auto-repair, CLI-only flows use asciinema recording.
Pipeline Context
/e2e-map → mapping.yaml (map UI elements)
/e2e-flow → flow.yaml + report (generate & verify)
/e2e-test → report.md (replay automated)
/e2e-walkthrough → flow.yaml (explore interactively)
Invocation
/e2e-flow [--from <source>] [--smoke] [--verify-only] [--mapping <name>] [--issue ID] [--no-verify] [--no-video] [--no-pr] [--no-teams]
| Arg | Effect |
|---|---|
| (no args) | Generate from current conversation context |
--from <file> |
Read a plan file, spec, or requirements doc |
--from pr <N> |
Read PR diff via gh pr diff |
--smoke |
Generate visit-all-pages flow from mapping |
--verify-only |
Skip generation, verify an existing flow in browser |
--mapping <name> |
Target a specific mapping (skip selection if only one) |
--issue ID |
Include issue context in report header |
--no-verify |
Generate flow only, skip browser verification |
--no-video |
Skip video recording during verification |
--no-pr |
Skip PR auto-detection, commit, and PR comment posting |
--no-teams |
Force subagent mode even when Agent Teams is available |
PR Mode (default)
PR mode is enabled by default. On invocation, auto-detect the current branch's PR:
gh pr view --json number,headRefName --jq '.number' 2>/dev/null
- PR found → PR mode active. Flow will be committed and results posted to PR.
- No PR / not a git repo /
ghunavailable → PR mode silently skipped (no error). --no-pr→ PR mode explicitly disabled regardless of PR existence.
Knowledge Bootstrap (before mapping discovery)
Read accumulated patterns to inform flow generation and verification:
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 623 lines · 68 tokens per session scan A d689cec95304
e2e-flow is a skill published in the GitHub repository iamcxa/kc-claude-plugins (3 stars, last pushed today), licensed MIT. It adds 68 tokens to every session and 7,505 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
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…