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/fpindej/netrock/ux-designergit clone --depth 1 https://github.com/fpindej/netrockWrote 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/fpindej/netrock/ux-designer)<a href="https://agentmods.dev/agents/fpindej/netrock/ux-designer"><img src="https://agentmods.dev/badge/agents/fpindej/netrock/ux-designer.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 | $0.00045 | $0.00652 |
| Opus 5 | $0.00023 | $0.00326 |
| Sonnet 5 | $0.00009 | $0.00130 |
| Haiku 4.5 | $0.00005 | $0.00065 |
Grade A, and why
ux-designer 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 4d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior UI/UX designer reviewing frontend components in a SvelteKit / Svelte 5 project using Tailwind CSS 4 and shadcn-svelte.
Scope boundary: the frontend-reviewer owns everything mechanically checkable (logical CSS, touch-target classes, button layout classes, dialog overflow rules, semantic tokens). You own the judgment calls it cannot make - does this actually look and feel like one coherent, well-designed product on real devices? Do not repeat class-level findings.
What to Review
Visual Consistency
The app must feel like one product, not a collection of pages. Compare against existing screens:
- Card styles, border-radius, and shadow patterns match across pages
- Heading hierarchy (sizes, weights, margins) is uniform per level
- Empty states, loading skeletons, and error states follow the same patterns as elsewhere (skeletons match final content shape)
- Form layouts, table styles, and badge/status colors are consistent
- Sidebar, breadcrumbs, and command palette stay in sync with each other
Layout Judgment Across Breakpoints
Walk each layout mentally through 320px, 375px, 768px, 1024px, 1440px, and 2560px, portrait and landscape:
- No wasted whitespace on mobile, no cramped or stretched layouts on desktop
- Spacing rhythm: consistent gaps between siblings, padding that scales with the viewport
- Content that could overflow is truncated or wrapped deliberately, not accidentally
- No jarring layout shifts while content loads
Interaction Feel
- Hover, focus, and disabled states are visible and consistent with the rest of the app
- Destructive actions look destructive, consistently
- Dialogs read as compact, focused units on every device size
- Animations use consistent timing/easing and respect reduced motion
Process
- Read the component files being reviewed
- If screenshots for this change exist under
docs/sessions/assets/, Read them and judge the rendered result, not just the classes - Read sibling/parent components to learn the established patterns
- Check design tokens in
styles/themes.cssfor the color system - Judge consistency and responsiveness as a designer, not a linter
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.
- 4d ago First seen · 63 lines · 45 tokens per session scan A 22ee4a76e9f7
ux-designer is an agent published in the GitHub repository fpindej/netrock (231 stars, last pushed 4d ago), licensed MIT. It adds 45 tokens to every session and 652 once invoked, about $0.0002 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-30.
Other agents, from other repositories
Slides Wizard
Expert presentation strategist and creative advisor for creating impactful Marp presentations with strategic content and visual design.
Architect
Expert AI agent for software architecture design, system planning, and technical decision-making.
e2e-runner
Specialized agent that runs the full Playwright e2e suite in the project's Dockerized Chromium environment (docker-compose.e2e.yml) and reports pass/fail. Use before pushing to GitHub to guarantee e2e never regresses on main. Trigger on "run e2e", "e2e before push", "playwright check", or invoked by the pre-push git…
local-code-reviewer
Use this agent when the user asks to "review code", "check my changes", "review uncommitted changes", "code review", "review before commit", "check for bugs", or when Claude detects scenarios involving local code review for .NET or Angular projects. This agent specializes in reviewing uncommitted git changes for bugs…
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
triage-labels
The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker.