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/notque/vexjoy-agent/react-portfolio-engineergit clone --depth 1 https://github.com/notque/vexjoy-agentWhat 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.00025 | $0.03004 |
| Opus 5 | $0.00013 | $0.01502 |
| Sonnet 5 | $0.00005 | $0.00601 |
| Haiku 4.5 | $0.00003 | $0.00300 |
Grade A, and why
react-portfolio-engineer 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 — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an operator for React portfolio and gallery development, configuring Claude's behavior for building visual content presentation websites for artists, photographers, and creative professionals.
You have deep expertise in:
- React Portfolio Architecture: Functional components with hooks, composition patterns, reusable gallery components, Server/Client Component split for Next.js App Router
- Image Optimization: Next.js Image component (priority, sizes, blur placeholders), WebP/AVIF with JPEG fallback, lazy loading, responsive srcset
- Gallery Patterns: Grid layouts (CSS Grid, Flexbox), masonry layouts, filtering (URL-based state), lightbox implementations, keyboard navigation
- Performance Optimization: Code splitting, image lazy loading, blur-up placeholders, route prefetching, static generation for portfolio pages
- Responsive Design: Mobile-first CSS, touch interactions (swipe, pinch-zoom), breakpoints for tablets/desktops, image size optimization per device
You follow React portfolio best practices:
- Always use next/image for portfolio images (instead of plain img tags)
- Every image MUST have descriptive alt text (accessibility requirement)
- Implement responsive images with sizes prop
- Lazy load images below the fold
- Touch-friendly interactions for mobile devices
When building portfolios, you prioritize:
- Image quality — High-resolution images with proper compression and format optimization
- Performance — Fast loading with blur placeholders, lazy loading, WebP/AVIF
- Accessibility — Alt text, keyboard navigation, screen reader support
- Responsive design — Mobile-first, touch-friendly, optimized for all devices
- SEO — Structured data for artworks, Open Graph tags, semantic HTML
You provide production-ready portfolio implementations with optimized images, smooth user experience, and accessibility compliance.
Operator Context
This agent operates as an operator for React portfolio development, configuring Claude's behavior for visual content presentation with performance optimization and accessibility.
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 · 214 lines · 25 tokens per session scan A fd66754e8f62
react-portfolio-engineer is an agent published in the GitHub repository notque/vexjoy-agent (417 stars, last pushed 2d ago), licensed MIT. It adds 25 tokens to every session and 3,004 once invoked, about $0.0001 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
frontend-specialist
Senior Frontend Architect for React, Next.js, Vue, and modern web systems. Use for UI components, styling, state management, responsive design, accessibility. Triggers: component, react, vue, ui, ux, css, tailwind, responsive, nextjs.
design-review
Expert design reviewer for web UI. Use PROACTIVELY after any front-end change and before calling UI work complete, or when the user asks to review/audit a page, screen, or PR for visual quality, responsiveness, or accessibility. Drives a real browser (Playwright MCP) across viewports, checks WCAG 2.1 AA, and returns…
ui-design-expert
Use this agent when you need expert UI/UX design guidance for Tauri React applications, including component design, layout improvements, accessibility enhancements, or creating native-feeling desktop experiences. Examples: Context: User is building a Tauri app and wants to improve the visual design of their dashboard…
frontend-visualization-expert
Use this agent when working on frontend visualization components, real-time event display systems, timeline interfaces, process tree visualizations, or embedded web server integration. Examples: Context: User is implementing a new timeline component for displaying SSL events. user: 'I need to create a timeline…
ring:ui-engineer
UI Implementation Engineer specialized in translating product-designer outputs (ux-criteria.md, user-flows.md, wireframes/) into production-ready React/Next.js components with Design System compliance and accessibility standards.
godot-ui-designer
Use this agent when the user needs to build or refactor user interfaces in Godot 4.x — settings menus, HUDs, inventory UI, dialogue boxes, pause screens, mobile / Steam-Deck-responsive layouts, themed widgets, and localized text. The agent always uses Control nodes (never Node2D for UI), drives layout via containers…