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/jansenanalytics/claudex/flow-testernpx skills add JansenAnalytics/claudex --skill flow-testergit clone --depth 1 https://github.com/JansenAnalytics/claudexWrote 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/jansenanalytics/claudex/flow-tester)<a href="https://agentmods.dev/skills/jansenanalytics/claudex/flow-tester"><img src="https://agentmods.dev/badge/skills/jansenanalytics/claudex/flow-tester.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.00052 | $0.01225 |
| Opus 5 | $0.00026 | $0.00613 |
| Sonnet 5 | $0.00010 | $0.00245 |
| Haiku 4.5 | $0.00005 | $0.00122 |
Grade A, and why
flow-tester 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 yesterday.
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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
flow-tester — End-to-End User Journey Tester
Playwright-based tool for testing multi-step user flows. Tests that complete user journeys work, not just individual pages.
Quick Start
# Run a flow definition
flow-tester run flow.json
# Auto-generate and run a flow from a URL
flow-tester review https://example.com --generate
# Generate flow from text description
flow-tester gen --describe "login with email [email protected] password 123, click Dashboard"
# Generate flow from URL (inspect page, find forms/links)
flow-tester gen https://myapp.com --output flow.json
# Generate report from results
flow-tester report ~/.flow-tester/results/<timestamp>/
Flow Definition Format
{
"name": "User Registration Flow",
"baseUrl": "http://localhost:5173",
"timeout": 30000,
"steps": [
{ "name": "Navigate to signup", "action": "goto", "url": "/signup" },
{ "name": "Fill email", "action": "fill", "selector": "input[name=email]", "value": "[email protected]" },
{ "name": "Click submit", "action": "click", "selector": "button[type=submit]" },
{ "name": "Verify redirect", "action": "assert", "type": "url-contains", "value": "/dashboard" },
{ "name": "Check welcome", "action": "assert", "type": "text-visible", "value": "Welcome" }
]
}
Supported Actions
| Action | Key Properties | Description |
|---|---|---|
goto |
url |
Navigate (relative to baseUrl or absolute) |
click |
selector |
Click element |
fill |
selector, value |
Clear + type into input |
type |
selector, value, delay? |
Type char-by-char (autocomplete) |
select |
selector, value |
Select dropdown option |
hover |
selector |
Hover over element |
scroll |
selector or x,y |
Scroll to element/position |
wait |
type, value/selector |
Wait for condition (selector/url/text/network-idle/time) |
screenshot |
filename?, fullPage? |
Capture screenshot |
keyboard |
key |
Press key (Enter, Tab, Escape, etc.) |
evaluate |
expression, expected? |
Run JS in page context |
upload |
selector, file/files |
Upload file(s) |
cookie |
operation (set/get/clear) |
Manage cookies |
localStorage |
operation, key?, value? |
Manage localStorage |
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.
- yesterday First seen · 125 lines · 52 tokens per session scan A 326abffee06c
flow-tester is a skill published in the GitHub repository JansenAnalytics/claudex (5 stars, last pushed 2mo ago), licensed MIT. It adds 52 tokens to every session and 1,225 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
e2e-automator
Build robust end-to-end test suites with Playwright or Cypress. Covers page objects, fixtures, visual testing, and CI integration.
BrowserBash Browser Automation
BrowserBash is a vendor-independent, natural-language browser automation CLI. Drive a real browser from plain-English objectives or committable Markdown tests, run on local Chrome, CDP/Playwright MCP, Browserbase, LambdaTest, or BrowserStack, and stream NDJSON results with CI exit codes — using free local Ollama…
glance-test
Run E2E browser tests on any web application using Glance MCP. Use when the user says "test this page," "check this URL," "run E2E tests," "browser test," "test the login flow," "check if the site works," "visual regression," or "screenshot this page." Also use for post-deploy verification and smoke tests.
reviewing-flows
Use when the pending flow queue needs triage before approval, such as deciding which recorded flows are worth keeping, clearing out ones that can never replay, or reading a flow's real steps before consenting to it.
author
Use when writing a new E2E browser test from a vague user description or feature requirement. Turns exploratory browser sessions into structured, reusable test cases.
runner
Use when executing a stable E2E test case that has already been refined. Follows test steps exactly without deviation, reports pass/fail with evidence.