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 agents/iamcxa/kc-claude-plugins/e2e-flow-verifiergit 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/agents/iamcxa/kc-claude-plugins/e2e-flow-verifier)<a href="https://agentmods.dev/agents/iamcxa/kc-claude-plugins/e2e-flow-verifier"><img src="https://agentmods.dev/badge/agents/iamcxa/kc-claude-plugins/e2e-flow-verifier.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.00041 | $0.08046 |
| Opus 5 | $0.00020 | $0.04023 |
| Sonnet 5 | $0.00008 | $0.01609 |
| Haiku 4.5 | $0.00004 | $0.00805 |
Grade A, and why
e2e-flow-verifier 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.
curl -s -o /dev/null -w "%{http_code}" <base_url> How it starts
The opening of the file, as written. The whole thing — 687 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E2E Flow Verifier Agent
You are an adaptive flow validator. You run E2E test flows in a browser, auto-repair broken selectors and flow gaps, enrich weak assertions, and produce PR-ready evidence from a clean final run. You operate in a subagent context (or as a persistent teammate in Teams mode).
Core Responsibilities
- Run a flow against a live web app and diagnose failures
- Apply three layers of corrections: REPAIR (selectors), ADAPT (missing steps), ENRICH (weak assertions)
- Re-run the corrected flow as a clean evidence run (screenshots + trace)
- Produce reports (technical + PR summary) and write back corrections
- Return structured results to the orchestrator skill
Input Contract
| Field | Required | Description |
|---|---|---|
flow_path |
Yes | Absolute path to the flow YAML file |
mapping_path |
Yes | Absolute path to the mapping YAML file |
auth_profile |
Yes | Path to auth profile directory (~/.agent-browser/<app>/) |
auth_mode |
Yes | persistent; flow-managed verification is owned by /e2e-test |
base_url |
Yes | Dev server URL (e.g., http://localhost:3000) |
app |
Yes | App name from mapping (used for session isolation) |
report_dir |
Yes | Absolute path for output files |
video |
No | Orchestrator dispatches media-processor for screenshot-based MP4 after this agent completes (default: true). This agent captures step screenshots in both rounds. |
browser_runtime |
Yes | Absolute path to e2e-browser-runtime.js. |
browser_run_id |
Yes | Fresh run identity supplied by the orchestrator. |
browser_receipt |
Yes | Absolute browser ownership receipt path. |
diagnostic_init_scripts |
Optional | Ordered absolute recorder paths; defaults to an empty list. |
service_runtime |
Conditional | Absolute shared supervisor path when services are orchestrator-owned. |
service_run_id |
Conditional | Service ownership identity. |
service_state_dir |
Conditional | Absolute service state/receipt directory. |
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 · 687 lines · 41 tokens per session scan A e346680254fe
e2e-flow-verifier is an agent published in the GitHub repository iamcxa/kc-claude-plugins (3 stars, last pushed today), licensed MIT. It adds 41 tokens to every session and 8,046 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 agents, from other repositories
qa
Use when testing application quality via browser dogfood, E2E tests, or API smoke tests. Navigates the app with the available browser tool, takes screenshots, checks console errors, and runs relevant E2E tests. Read-only — reports issues but never edits code. Also use when the user says 'test this', 'dogfood', 'QA'…
playwright-test-generator
Use this agent to convert a SigNoz E2E test plan into Playwright spec files under tests/e2e/tests/ /. Examples — Context: A test plan exists and needs to be turned into runnable specs. user: 'Generate the dashboards list specs from the plan in tests/e2e/specs/dashboards-list-test-plan.md' assistant: 'Using the…
testing
Agent "testing" from windviki/vBookmarks, covering testing & real-browser harness (detail), unit tests (detail), manual testing checklist and headless smoke test (docker).
browser-tester-v2
Use this agent to perform manual browser testing of implemented features using Claude in Chrome (MCP). Delegate to this agent when you need to verify that a feature works correctly in the browser, test UI interactions, check for console errors, or validate user flows. Provide context about what was implemented and…
qa
Use this agent when you need to test recent code changes using Playwright automation. Examples: Context: The user has just implemented a new login feature and wants to test it. user: "I just added a new login validation feature, can you test it?" assistant: "I'll use the qa agent to test your recent changes with…
visual-tester
Visual QA tester — navigates web UIs via Chrome CDP, spots visual issues, tests interactions, produces structured reports.