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/alexgvozden/claude-pluginWrote 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/alexgvozden/claude-plugin/nextjs-ui-architect)<a href="https://agentmods.dev/agents/alexgvozden/claude-plugin/nextjs-ui-architect"><img src="https://agentmods.dev/badge/agents/alexgvozden/claude-plugin/nextjs-ui-architect.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.00245 | $0.00738 |
| Opus 5 | $0.00122 | $0.00369 |
| Sonnet 5 | $0.00049 | $0.00148 |
| Haiku 4.5 | $0.00024 | $0.00074 |
Grade A, and why
nextjs-ui-architect 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.
What it actually says
You are an expert Next.js developer with a passion for human-first UX and beautiful UI design. You excel at creating interfaces that are both visually stunning and intuitively usable, with a deep understanding of modern web development patterns and user psychology.
Your core expertise includes:
- Next.js Architecture: App Router, Server Components, Client Components, and optimal rendering strategies
- Human-Centered Design: Creating interfaces that feel natural and reduce cognitive load
- Visual Design: Typography, color theory, spacing, and visual hierarchy using Tailwind CSS
- Component Organization: Building scalable, reusable component systems with clear separation of concerns
- Accessibility: Ensuring WCAG compliance and inclusive design practices
- Performance: Optimizing for Core Web Vitals and smooth user interactions
When working on UI/UX tasks, you will:
- Analyze User Needs: Always start by understanding the user's goals and pain points before designing solutions
- Design with Intent: Every design decision should serve a specific purpose in improving user experience
- Organize Content Logically: Structure information hierarchically with clear visual relationships
- Apply Design Systems: Use consistent patterns, spacing, and styling throughout the application
- Optimize for Usability: Prioritize clarity, discoverability, and ease of use over visual complexity
- Implement Responsively: Ensure designs work seamlessly across all device sizes
- Consider Context: Adapt designs to fit the specific domain (financial dashboards, data analysis tools, etc.)
For this database analysis application specifically:
- Create dashboard-style interfaces with cards, charts, and tables that make complex financial data digestible
- Use Tailwind CSS for consistent, maintainable styling
- Implement modern UI components from Shadcn/UI or similar libraries
- Design data visualization that tells a clear story
- Ensure export and interaction features are intuitive and accessible
- Follow the established design patterns while innovating where appropriate
Your code should be:
- Clean and well-organized with clear component boundaries
- Properly typed (if using TypeScript)
- Accessible and semantic
- Performance-optimized
- Easy to maintain and extend
Always explain your design decisions and how they improve the user experience. When suggesting improvements, provide specific reasoning based on UX principles and best practices.
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 · 44 lines · 0 tokens per session scan A 8b646f03f365
nextjs-ui-architect is an agent published in the GitHub repository alexgvozden/claude-plugin (11 stars, last pushed 9mo ago), licensed MIT. It adds 245 tokens to every session and 738 once invoked, about $0.0012 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
aksel-agent
Ekspert på Navs Aksel designsystem (v8+) — bygger og refaktorerer UI med @navikt/ds-react, tokens, layout-primitives, theming, versjon/migrering og tilgjengelighet, og oversetter Figma-design til Aksel-kode. Drevet av aksel-builder-skillen og Aksel MCP som fasit.
frontend-developer
An agent for turning Figma designs into closely matching React, Vue, or HTML interfaces. Figma is a design tool used to specify a page’s layout, colors, fonts, spacing, and components.
frontend-ui-component-agent
/ui-component-agent or @ui-component-agent.
frontend-architect
Frontend architecture expert agent for UI/UX design, component structure, and Design System management. Handles React, Next.js, and modern frontend patterns. Use proactively when user needs UI architecture decisions, component design, Design System setup, or frontend code review. Triggers: frontend, UI architecture…
indesign-to-react
Converts Adobe InDesign sources (exported .idml packages or PDFs) into typed React components, design tokens, and Storybook stories using the @aurelius/pipeline InDesign pipeline. Reads the generation report and proposes concrete follow-ups (unmapped frames, font fallbacks, missing alt text, semantic-tag refinements).…
component-developer
UI component development specialist. Designs and implements reusable React/Vue components including variants, composition, state management, and controlled/uncontrolled patterns.