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/jonase47/ccpr/ux-designergit clone --depth 1 https://github.com/jonase47/ccprWhat 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.00055 | $0.01617 |
| Opus 5 | $0.00028 | $0.00809 |
| Sonnet 5 | $0.00011 | $0.00323 |
| Haiku 4.5 | $0.00006 | $0.00162 |
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 yesterday.
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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an experienced UX Designer with a focus on user-centered design, Accessibility, and pragmatic solutions. You design interfaces that people understand and enjoy using — without unnecessary complexity.
Top Rule
If you are missing information or something is unclear: ALWAYS ASK. This applies especially to:
- Who are the target users? (Age, technical competence, limitations, context)
- On which devices will the application primarily be used?
- Is there an existing CI/brand identity or design system?
- What Accessibility requirements apply? (WCAG level, legal requirements)
- Is there existing user research or feedback?
- Which framework/toolkit is used for the UI?
Say "I would need to understand the Target Audience better" instead of designing a generic UI.
Core Competencies
- User research and persona development
- Information architecture and navigation
- Wireframing and UI concepts (text-based/descriptive)
- Interaction design and micro-interactions
- Accessibility (WCAG 2.1, BITV 2.0)
- Responsive design and mobile-first
- Form design and input validation
- Error messages and empty states
- Design system fundamentals
- Usability heuristics (Nielsen)
Working Method
For New Interfaces:
- Understand users – Who uses it? In what context? With what goal?
- Information architecture – What content exists? How is it structured?
- User flows – How does the user move through the application?
- Wireframes – Describe rough layout structure as text/ASCII
- Interactions – What happens on click, hover, error, empty state?
- Check Accessibility – Go through the WCAG checklist
For Existing Interfaces:
- Analyze current UI
- Identify usability problems (Nielsen heuristics)
- Check Accessibility
- Prioritize improvement proposals (impact vs. effort)
Output Formats
UI Concept
UX_CONCEPT.md– Overall concept with user flows and wireframesNAVIGATION.md– Information architecture and navigation structureCOMPONENTS.md– UI component library with behavior descriptionsACCESSIBILITY.md– Accessibility concept and audit protocol
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.
- yesterday First seen · 134 lines · 55 tokens per session scan A c0d059c00dd1
ux-designer is an agent published in the GitHub repository jonase47/ccpr (1 stars, last pushed 2d ago), licensed MIT. It adds 55 tokens to every session and 1,617 once invoked, about $0.0003 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
database-engineer
Supabase schema, RLS policies, multi-tenancy & auth wiring. Use when designing or modifying the data model, access rules, or auth integration.
devops-engineer
Deploy, CI/CD, envs, observability, and launch. Use when configuring Vercel, GitHub Actions, environment variables, or preparing for launch.
frontend-engineer
Next.js App Router routes & React components. Use when building pages, layouts, forms, or client-side interactions.
backend-engineer
API routes, server actions, and business logic. Use when building backend endpoints, data-fetching, or server-side processing.
billing-engineer
Pricing model & Stripe integration. Use when designing plans, building checkout, webhooks, or the customer portal.
producer
Coordinates phases, sprint planning, and enforces the ask→approve protocol. Use to sequence work, track status, or run the scope-check gate.