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 skills/everyone-needs-a-copilot/claude-copilot/ux-patternsnpx skills add Everyone-Needs-A-Copilot/claude-copilot --skill ux-patternsgit clone --depth 1 https://github.com/Everyone-Needs-A-Copilot/claude-copilotWrote 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/skills/everyone-needs-a-copilot/claude-copilot/ux-patterns)<a href="https://agentmods.dev/skills/everyone-needs-a-copilot/claude-copilot/ux-patterns"><img src="https://agentmods.dev/badge/skills/everyone-needs-a-copilot/claude-copilot/ux-patterns.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.00099 | $0.01712 |
| Opus 5 | $0.00049 | $0.00856 |
| Sonnet 5 | $0.00020 | $0.00342 |
| Haiku 4.5 | $0.00010 | $0.00171 |
Grade A, and why
ux-patterns 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 today.
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 — 280 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UX Patterns
Patterns for designing task flows, service blueprints, wireframes, and user interactions with comprehensive state coverage.
Purpose
Provides patterns for:
- Task flows with all user paths
- Service blueprints (frontstage/backstage)
- Wireframe specifications
- Error and empty state design
- Accessibility from the start
Core Patterns
Pattern 1: Task Flow Structure
When to use: Defining any user interaction flow.
Implementation:
## Task Flow: [Name]
**User Goal:** What they want to accomplish
**Entry Point:** Where they start
**Success:** How they know they succeeded
### Primary Path
1. [Action] -> [Response] -> [State]
2. [Action] -> [Response] -> [State]
3. [Action] -> [Response] -> [Success]
### Alternative Paths
- [Condition] -> [Alternative flow]
### Error States
| Error | Message | Recovery |
|-------|---------|----------|
| [Error] | [What happened + How to fix] | [User action] |
Benefits:
- Clear success criteria
- All paths documented
- Error recovery built-in
Pattern 2: Service Blueprint
When to use: Mapping end-to-end service experiences.
Implementation:
## Service Blueprint: [Name]
### Journey Stages
[Awareness] -> [Consideration] -> [Purchase] -> [Use] -> [Support]
### Customer Actions (per stage)
| Stage | Actions |
|-------|---------|
| [Stage] | [What customer does] |
### Frontstage (Visible)
| [Touchpoint] | [Touchpoint] | [Touchpoint] |
### Line of Visibility
---
### Backstage (Invisible)
| [Process] | [Process] | [Process] |
### Support Processes
| [System] | [System] | [System] |
### Pain Points
- **[Stage]:** [Issue] - [Evidence]
### Opportunities
- **[Stage]:** [Improvement] - [Impact]
Pattern 3: State Coverage Matrix
When to use: Ensuring all UI states are designed.
Implementation:
| State | When | Content | Action |
|---|---|---|---|
| Default | Normal use | Full content | Primary action |
| Loading | Fetching data | Skeleton/spinner | Disabled actions |
| Empty | No data yet | Why empty + CTA | Create/Add action |
| Error | Operation failed | What + How to fix | Retry/Fix action |
| Success | Action completed | Confirmation | Next action |
| Partial | Some data | Available content | Load more |
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.
- today First seen · 280 lines · 99 tokens per session scan A 8e03c847e0c7
ux-patterns is a skill published in the GitHub repository Everyone-Needs-A-Copilot/claude-copilot (13 stars, last pushed 10d ago), licensed MIT. It adds 99 tokens to every session and 1,712 once invoked, about $0.0005 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-09-04.
Other skills, from other repositories
wireframe
Produce low-fidelity black-and-white UI wireframes as SVGs or viewer pages. Use when asked to wireframe, sketch a screen, draft a layout, make a low-fi mockup, or publish wireframes.
browser
Full browser capability — managed Browsie session or emergency Main direct mode.
frontend-design
Design and implement context-fit frontend interfaces with deliberate art direction, accessible interaction, responsive behavior, complete states, and rendered verification. Use when creating or substantially reworking pages, components, product workspaces, dashboards, marketing sites, editorial surfaces, commerce…
Form UX Optimizer
Reviews web forms for usability issues — field ordering, validation messages, error states, and accessibility.
design-system
Document and define UI design system tokens, components, and guidelines.
web-design
UI review against Web Interface Guidelines. Use when asked to review UI, check accessibility, or audit design.