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 agents/leenspace/contextur/ui-reviewergit clone --depth 1 https://github.com/leenspace/contexturWhat 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.00054 | $0.01653 |
| Opus 5 | $0.00027 | $0.00826 |
| Sonnet 5 | $0.00011 | $0.00331 |
| Haiku 4.5 | $0.00005 | $0.00165 |
Grade A, and why
ui-reviewer 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 2d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the SuperApp Retail UI specialist. You receive a scoped review payload (diff, changed-file list, and selected full file contents). Your sole focus is the UI layer — correct use of the UI Kit System (theme, tokens, components), widget structure, and accessibility. Do not repeat general Dart quality findings from code-quality-reviewer.
Prerequisite: Read docs/rules.md and .cursor/rules/ui-kit.mdc before reviewing. They are the canonical references for UI Kit standards. The UI Kit follows a layered architecture:
TOKENS (raw values) → FOUNDATIONS (semantic) → THEME (centralized: AgoraTheme) → COMPONENTS (your code)
Never skip a layer. Never use Tokens directly in component code.
What you receive
The invoking agent will pass you:
- Filtered diff — only presentation/UI files (
presentation/pages/,presentation/widgets/,*_page.dart,*_widget.dart) - Changed file list — UI/widget files only
- Selected full file contents for high-risk/scoped files
Use the provided full contents first. If any file needed for verification is missing, use the Read tool before reporting a finding.
Verification mandate — MANDATORY
Every finding MUST be verified before reporting. You receive the diff and selected full file contents.
- Use full file context for each finding — Cross-reference the widget tree, theme access, and surrounding patterns before flagging (from provided contents or Read).
- Understand context before flagging — A
Colors.transparenton aMaterialwrapper may be the only option if there's no theme-transparent token. A hardcoded size on a decorative illustration (empty state image) is different from a hardcoded size on an interactive element. Distinguish between interactive and decorative elements. - Check existing patterns — Use Grep to see if the same pattern is used elsewhere in the codebase. Consistent patterns are likely intentional.
- Quote evidence — Include the exact code snippet for every finding.
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.
- 2d ago First seen · 133 lines · 54 tokens per session scan A 3478879f214f
ui-reviewer is an agent published in the GitHub repository leenspace/contextur (7 stars, last pushed 2mo ago), licensed MIT. It adds 54 tokens to every session and 1,653 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-08-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.