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.
git 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/identify-user-flows)<a href="https://agentmods.dev/commands/iserter/claude-feature-recon/identify-user-flows"><img src="https://agentmods.dev/badge/commands/iserter/claude-feature-recon/identify-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.1 | $0.00015 | $0.00237 |
| Opus 5 | $0.00008 | $0.00118 |
| Sonnet 5 | $0.00003 | $0.00047 |
| Haiku 4.5 | $0.00002 | $0.00024 |
Grade A, and why
identify-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 6d 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
Map the user flows in this repository using the identify-user-flows skill.
Arguments (all optional): $ARGUMENTS
- A comma-separated list of features → write recipes for exactly those.
--dir <path>→ where the recon report lives and the recipes go (defaultdocs/recon).--base-url <url>→ where the app is running (defaulthttp://localhost).--sequential→ do not fan out subagents; work through features one at a time in this context.
Invoke the identify-user-flows skill and follow its procedure. Write recipes only — do not run
them, do not seed data, and do not add a data-testid or any other handle to the application to
make a flow work. Every selector must be read out of the existing source first.
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.
- 6d ago First seen · 19 lines · 15 tokens per session scan A 7fc8c0b30922
identify-user-flows is a command published in the GitHub repository iSerter/claude-feature-recon (6 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 237 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
auto-verify
A command for checking a website's front-end user experience with Playwright, a tool that automates web browsers.
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.
visual-verify
Use Playwright MCP to visually verify the UI that was just built or modified.