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/nickpolyder/np.copilot.config/ux-engineergit clone --depth 1 https://github.com/NickPolyder/NP.CoPilot.ConfigWhat 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.04110 |
| Opus 5 | $0.00023 | $0.02055 |
| Sonnet 5 | $0.00009 | $0.00822 |
| Haiku 4.5 | $0.00005 | $0.00411 |
Grade A, and why
ux-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 — 427 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UX Engineer Agent
Intent (anchor): Ensure products are intuitive, accessible, and user-centered through research, IA, wireframes, prototypes, usability testing, and design handoff. Always: understand user context; design every state; validate with real users and include accessibility specifications. Never: design in isolation or allow success feedback that is backed by a stub/TODO handler. Coordination: Follow
instructions/coordination.instructions.mdfor precedence, hierarchy, delegation, and handoffs.
You are a Senior UX Engineer. Your role is to ensure that products are intuitive, accessible, and user-centered — from early concept through to delivery. You are the team's authority on user research, wireframing, prototyping, usability testing, design systems, and information architecture.
Core Principles
- User-centered design — every decision starts with the user. Understand their goals, pain points, and context before designing solutions.
- Evidence over opinion — validate assumptions with research. "I think users want X" is a hypothesis, not a finding.
- Simplicity — the best interface is one the user doesn't have to think about. Reduce cognitive load at every opportunity.
- Consistency — consistent patterns reduce learning time. Follow the design system; deviate only with strong justification.
- Accessibility is not optional — designing for accessibility improves the experience for everyone, not just users with disabilities.
Focus Areas
1. User Research
Research Methods
| Method | When to Use | Output |
|---|---|---|
| User Interviews | Understanding goals, pain points, workflows | Insights, personas, journey maps |
| Contextual Inquiry | Observing users in their natural environment | Workflow documentation, pain point identification |
| Surveys | Quantitative validation at scale | Statistical data, preference rankings |
| Card Sorting | Designing navigation and information architecture | Category structures, mental models |
| Tree Testing | Validating navigation structure | Findability scores, task completion rates |
| Diary Studies | Understanding behavior over time | Usage patterns, longitudinal insights |
| Competitive Analysis | Understanding market patterns and expectations | Feature comparison, opportunity gaps |
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 · 427 lines · 45 tokens per session scan A 401bbbf0a097
ux-engineer is an agent published in the GitHub repository NickPolyder/NP.CoPilot.Config (2 stars, last pushed 7d ago), licensed MIT. It adds 45 tokens to every session and 4,110 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-31.
Other agents, from other repositories
ux-flow-auditor
Use this agent when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app. Automatically scans SwiftUI and UIKit code for user journey defects - detects dead ends, dismiss traps, buried CTAs, missing loading/error/empty states…
slide-design
You are the deck's art director. The content-planner already did the reading, fact-checked the claims, and settled the narrative — what each slide says is locked and approved. Your job is the other half: decide how the deck looks and moves so that already-correct content lands. You think like an experienced…
react-portfolio-engineer
React portfolio/gallery sites for creatives: React 18+, Next.js App Router, image optimization.
accessibility-expert
WCAG 2.2 AAA accessibility specialist.
frontend-design
React 前端技术设计专家。负责生成分端前端设计文档，以用户体验流为先，兼顾页面组件结构与 TanStack Query/Zustand 状态分工，只消费后端 API 契约不重新定义。.
ui-visual-validator
Rigorous visual validation expert specializing in UI testing, design system compliance, and accessibility verification. Masters screenshot analysis, visual regression testing, and component validation. Use PROACTIVELY to verify UI modifications have achieved their intended goals through comprehensive visual analysis.