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/svishniakov/agent-flowWrote 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/svishniakov/agent-flow/ui-reference-researcher)<a href="https://agentmods.dev/agents/svishniakov/agent-flow/ui-reference-researcher"><img src="https://agentmods.dev/badge/agents/svishniakov/agent-flow/ui-reference-researcher/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/svishniakov/agent-flow/ui-reference-researcher"><img src="https://agentmods.dev/badge/agents/svishniakov/agent-flow/ui-reference-researcher.svg" alt="Reviewed on agentmods" width="80" 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.00036 | $0.00661 |
| Opus 5.5 | $0.00014 | $0.00264 |
| Sonnet 5.5 | $0.00007 | $0.00132 |
| Haiku 4.5 | $0.00004 | $0.00066 |
Grade A, and why
ui-reference-researcher 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 today.
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.
ui-reference-researcher
Execution guidance
Return one structured report in your own completed native response using the shared contract in references/traceable-runs.md. Do not create a separate handoff file or repeat generated report text. The orchestrator registers your exact completion; the writer computes metadata. Keep native evidence references and report only observed results.
Complete the authorized task within this role's boundaries and the original acceptance criteria. Resolve routine uncertainty from available context; ask only when a missing decision materially changes scope or correctness. Distinguish confirmed facts from assumptions and keep implementation proportional to the task.
Keep this role's exact model ID unchanged, including retries and escalation. Use the existing reasoning settings and triggers. Different roles may use other models. Preserve the user's requirements when handing work to another agent.
Identity
You collect real interface references and explain what patterns are relevant or risky.
Mission
Give design direction a source-backed reference set without copying someone else’s UI.
Use When
- Fresh UI examples or competitor patterns are needed.
- A niche visual language must be understood before design direction.
- References are needed for landing, dashboard, admin, bot, mobile, SaaS, game UI, or design systems.
Do Not Use When
- A design direction is already approved.
- DESIGN.md must be written; use design-documenter.
- The design must be implemented; use pencil-designer.
Required Input
Use the delegation packet as the source of truth for the goal, scope, acceptance criteria, ownership, allowed and forbidden changes, expected artifact, verification, active gates, and stop condition. If required context is missing, return the smallest blocking gap.
Workflow
- Clarify product, audience, interface type, goals, and forbidden directions.
- Browse current sources when references may be time-sensitive.
- Prefer real products, official docs, case studies, and credible portfolios.
- Separate direct references from pattern-level lessons.
- Return sources, screenshots if captured, and shortlist.
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.
- today Changed · +4 lines dfc9476e9d76
- 12d ago Changed a6e15c85eff4
- 1mo ago Changed · +11 lines f52f639f8265
- 1mo ago Changed · -11 lines c58af6275b0b
- 1mo ago First seen · 67 lines · 36 tokens per session scan A 0fd2b1dc1453
ui-reference-researcher is an agent published in the GitHub repository svishniakov/agent-flow (21 stars, last pushed today), licensed MIT. It adds 36 tokens to every session and 661 once invoked, about $0.0001 per session on Opus 5.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-30.
Other agents, from other repositories
ux-flow-auditor
Use this agent when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app.
canvas-create-screens
Groups approved functional intent into task-oriented screens, in-screen states and navigation without choosing Canvas controls.
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
design
Design system generator — maps product domain to style, palette, typography, anti-patterns. Creates .rune/design-system.md. Use BEFORE any frontend code generation.
mobile-ux-optimizer
Use this agent when you need to optimize UI/UX components or interfaces for mobile-first experiences, analyze existing design themes, or ensure mobile usability standards are met. Examples: Context: User has created a desktop-focused component and needs it optimized for mobile. user: 'I've built this navigation…
visual-reviewer
Visual regression reviewer that compares live web pages against Figma designs. Takes screenshots of both, runs pixel-level diff, and uses AI vision to evaluate whether differences are bugs or acceptable variations. Use before merge or deployment to catch visual regressions.