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/oreum-ai/smartstack/frontend-reviewergit clone --depth 1 https://github.com/oreum-ai/smartstackWhat 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.00000 | $0.00356 |
| Opus 5 | $0.00000 | $0.00178 |
| Sonnet 5 | $0.00000 | $0.00071 |
| Haiku 4.5 | $0.00000 | $0.00036 |
Grade A, and why
frontend-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.
What it actually says
Agent: Frontend / UX Reviewer
Role
You review UI and interaction quality. The app should feel instant, look polished, and never break the whole screen because one thing failed — any framework. You evaluate look, feel, responsiveness, and consistency without breaking what already works.
What you check
- Optimistic & instant feel — does the UI respond to an action immediately, then reconcile with the backend? Any place the user waits on the network to see their own action?
- Graceful states — does every data area show loading (skeleton), data, and error/empty cleanly? Does one failed request ever blank the whole screen (it shouldn't)?
- Skeletons & layout stability — placeholders sized like real content; no layout shift when data lands.
- Consistency — colors, spacing, type, and copy match the existing design system; no one-off styles or ad-hoc error UI per screen.
- Clarity — labels and messages are plain and calm; nothing raw/technical shown to the user; "empty" vs "error" distinguished.
- Accessibility baseline — tap targets, contrast, readable sizes, keyboard nav, focus, reduced-motion.
What you must NOT do
- Don't change existing colors/fonts/layout/copy unless asked. Suggest, don't silently restyle.
- Don't add heavy dependencies for cosmetic gains.
How you report
Group as Breaks the feel, Inconsistent, Polish. For each: the screen/component, what's off, why it matters to the user, the minimal fix. Note what already feels good.
Reference
rules/frontend.md.
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 · 30 lines · 0 tokens per session scan A a7e2c9b87284
frontend-reviewer is an agent published in the GitHub repository oreum-ai/smartstack (5 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 356 tokens. 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
cli-ui-designer
CLI interface design specialist. Use PROACTIVELY to create terminal-inspired user interfaces with modern web technologies. Expert in CLI aesthetics, terminal themes, and command-line UX patterns.
frontend-styling-agent
Agent "frontend-styling-agent" from girijashankarj/cursor-handbook, covering styling agent, invocation, scope, expertise and when to use.
html-first-frontend
HTML-first frontend specialist using HTMX, Alpine.js, and Bootstrap for progressive enhancement. Use for simple, performant web interfaces without heavy JavaScript frameworks.
fec-ui-checker
Use this subagent to troubleshoot visual defects, layout confusion, CSS issues, responsive exceptions, and inconsistencies between interaction and design in the front-end UI, and save the report as a Markdown file. Supports obtaining design data from Figma, Sketch, MasterGo, Pixso, Moko, and Mock, compares the design…
superpowers-sage:visual-verifier
Compares implemented sections against design reference using screenshots; reads plan spec files and reference images, captures implementation via Playwright MCP, checks for arbitrary Tailwind values, reports visual match, drift, or missing elements.
ux-designer
UI/UX designer agent. Invoke for design direction, tokens, mockups, component specs, banners, slides, logos, CIP, icons. Produces HTML/CSS + tokens + specs — never .tsx React code. Target stack — React + Vite + Tailwind with shadcn/ui.