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 commands/iserter/claude-feature-recon/test-user-flowsgit clone --depth 1 https://github.com/iSerter/claude-feature-reconWrote 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/commands/iserter/claude-feature-recon/test-user-flows)<a href="https://agentmods.dev/commands/iserter/claude-feature-recon/test-user-flows"><img src="https://agentmods.dev/badge/commands/iserter/claude-feature-recon/test-user-flows.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.00017 | $0.00276 |
| Opus 5 | $0.00009 | $0.00138 |
| Sonnet 5 | $0.00003 | $0.00055 |
| Haiku 4.5 | $0.00002 | $0.00028 |
Grade A, and why
test-user-flows 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.
What it actually says
Run this repository's user flows against the live application using the test-user-flows skill.
Arguments (all optional): $ARGUMENTS
--dir <path>→ where the recipes and the report live (defaultdocs/recon).--feature <slug>/--only <flowId>→ run a subset. Results for flows you did not run are kept.--headed→ watch the browser do it.--retries 1→ retry a failed flow once, to tell a real defect from a race.--no-findings→ record the run only; skip the triage pass that writesfeatures/{slug}.e2e.json.
Invoke the test-user-flows skill and follow its procedure. Do not fix anything you find, do not
loosen an assertion to make a flow pass, and do not seed data without asking — this produces the
results and the findings only.
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 · 20 lines · 17 tokens per session scan A 2676ec5ee44b
test-user-flows is a command published in the GitHub repository iSerter/claude-feature-recon (6 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 276 once invoked, about $0.0001 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 commands, from other repositories
expect
Diff-aware AI browser testing — reads the git diff, maps changes to affected pages via the route map, generates a targeted test plan, and executes it via agent-browser (Rust daemon + CDP, ARIA-tree-first) with pass/fail reporting. Use when testing UI changes, verifying PRs before merge, or running regression checks on…
auto-verify
프론트엔드 UX 검증 — Playwright 기반 비주얼 검증을 실행합니다.
buildable-preview
Render the running prototype in a headless browser, screenshot it, and catch runtime/visual errors.
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.
record
Record a browser walkthrough of a URL using Antigravity (agy). Generates .webm video, screenshots, and a report. Auto-converts to MP4 if ffmpeg is available.
vibereview
Legacy alias for the focused Randroid VibeReview skill.