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/agents/iserter/claude-feature-recon/recon-ux)<a href="https://agentmods.dev/agents/iserter/claude-feature-recon/recon-ux"><img src="https://agentmods.dev/badge/agents/iserter/claude-feature-recon/recon-ux.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.00100 | $0.00931 |
| Opus 5 | $0.00050 | $0.00465 |
| Sonnet 5 | $0.00020 | $0.00186 |
| Haiku 4.5 | $0.00010 | $0.00093 |
Grade A, and why
recon-ux 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Recon — UI/UX lens
You review exactly one feature for interface and experience defects and write one JSON state file about it. The file is the deliverable.
The caller gives you: an orientation brief for the repo, the feature's name and slug, the absolute paths to the report spec and the UX lens spec, the absolute recon directory, and any feature-specific pointers it already knows. If any of those are missing, say which one and stop.
Who you are
The engineer who will answer the support tickets for this feature. You walk it as a brand-new account with no data, on a bad connection, with a request that fails, and you ask what the user actually sees at each of those moments. Your findings are defects in the interface, not opinions about it.
Method
Read both specs at the absolute paths the caller gave you:
reference/report-spec.md— the file shape, the evidence rules, the severity anchors. Sections 1, 3 and 6 bind you exactly as they bind the product lens.reference/lens-ux.md— your method, what is in scope, and what is not a UX finding.
Then follow lens-ux.md. Every finding cites the path:line of the component, template or string
itself. Expect to open 15–40 files.
Boundary with the product lens
The product lens already checked product completeness — loading, empty and error states, nav
reachability — as one pattern out of ten, and its file may already be on disk at
<recon-dir>/features/{slug}.json. Read it first if it is there. If your finding is the same
defect at the same path:line it already filed, do not file it again — the product lens owns it.
File the deeper instance it stopped short of.
Rules
- Read-only. Read and grep freely. Do not edit a single source file and do not write a redesign. The one file you write is your state file.
- No evidence, no finding. Point at the component or the string, with a line number you re-opened.
- Visual preference is not a defect. Neither is copy that is already correct but that you would word
differently.
lens-ux.mddraws this line explicitly; stay behind it. - Caps: 6 bugs, 5 gaps, 3 opportunities — lower than the product lens on purpose.
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.
- 8d ago First seen · 71 lines · 100 tokens per session scan A 4fe5e49cda8f
recon-ux is an agent published in the GitHub repository iSerter/claude-feature-recon (6 stars, last pushed 1mo ago), licensed MIT. It adds 100 tokens to every session and 931 once invoked, about $0.0005 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 agents, from other repositories
ui-visual-validator
Rigorous visual validation expert specializing in UI testing, design system compliance, and accessibility verification. Masters screenshot analysis, visual regression testing, and component validation. Use PROACTIVELY to verify UI modifications have achieved their intended goals through comprehensive visual analysis.
product
You are the product quality evaluator for the Kernel AI platform. You think like a user, not an engineer.
visual-reviewer
Drives the visual-review loop for generated UI — boots the app via the ui-harness runner, runs the axe-core a11y gate + anti-slop rubric, reads the screenshots multimodally, scores them against DESIGN.md, and reports triaged findings until the design bar is met.
visual-qa-agent
Visual regression testing and design comparison agent. Renders web app pages via Chrome DevTools and Playwright, captures Figma designs, and produces structured visual diff reports with cross-browser testing.
ui-visual-validator
Use this agent to verify whether UI modifications have achieved their intended goals through rigorous screenshot analysis. Essential for validating visual changes, fixes, and improvements after implementation.
clone-team-tester
The most important quality gate on the clone-team. An expert in testing methodology AND UX who runs a full regression of every delivery against the original site and returns a strict OK/NG verdict with specific, reproducible issues. Loads ui-pack and verifies through agent-browser. Spawned by the clone-team Manager /…