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/design-patternsnpx skills add Everyone-Needs-A-Copilot/claude-copilot --skill design-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/design-patterns)<a href="https://agentmods.dev/skills/everyone-needs-a-copilot/claude-copilot/design-patterns"><img src="https://agentmods.dev/badge/skills/everyone-needs-a-copilot/claude-copilot/design-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.1 | $0.00093 | $0.01699 |
| Opus 5 | $0.00046 | $0.00849 |
| Sonnet 5 | $0.00019 | $0.00340 |
| Haiku 4.5 | $0.00009 | $0.00170 |
Grade A, and why
design-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 — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Patterns
Visual design patterns for creating consistent, accessible interfaces with proper design tokens and component specifications.
Purpose
Provides patterns for:
- Design token systems (colors, typography, spacing)
- Component visual specifications
- WCAG 2.1 AA accessibility compliance
- Responsive design across breakpoints
Core Patterns
Pattern 1: Semantic Color Tokens
When to use: Defining color systems that work across themes.
Implementation:
/* Base palette (reference only) */
--blue-500: #3b82f6;
--blue-700: #1d4ed8;
/* Semantic tokens (use these) */
--color-primary: var(--blue-500);
--color-primary-hover: var(--blue-700);
--color-text: #111827;
--color-text-muted: #6b7280;
--color-background: #ffffff;
--color-error: #ef4444;
--color-success: #10b981;
Benefits:
- Theme switching via semantic tokens
- Consistent color usage across components
- Easier maintenance and updates
Pattern 2: 8px Spacing Scale
When to use: All spacing decisions (padding, margins, gaps).
Implementation:
--space-1: 0.25rem; /* 4px - tight */
--space-2: 0.5rem; /* 8px - compact */
--space-3: 0.75rem; /* 12px */
--space-4: 1rem; /* 16px - default */
--space-6: 1.5rem; /* 24px - medium */
--space-8: 2rem; /* 32px - large */
--space-12: 3rem; /* 48px - section */
Benefits:
- Visual rhythm and consistency
- Predictable spacing relationships
- Easier to maintain
Pattern 3: Component State Matrix
When to use: Defining all interactive component states.
Implementation:
| State | Background | Border | Text | Cursor |
|---|---|---|---|---|
| Default | --color-bg |
--color-border |
--color-text |
default |
| Hover | --color-bg-hover |
--color-border |
--color-text |
pointer |
| Focus | --color-bg |
--color-focus-ring |
--color-text |
— |
| Active | --color-bg-active |
--color-border |
--color-text |
pointer |
| Disabled | --color-bg |
--color-border |
--color-text-muted |
not-allowed |
| Loading | --color-bg |
--color-border |
--color-text-muted |
wait |
| Error | --color-bg |
--color-error |
--color-error |
— |
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 · 223 lines · 93 tokens per session scan A ba2f253925ca
design-patterns is a skill published in the GitHub repository Everyone-Needs-A-Copilot/claude-copilot (13 stars, last pushed today), licensed MIT. It adds 93 tokens to every session and 1,699 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
design-system
Document and define UI design system tokens, components, and guidelines.
design-md
Author/validate/export Google's DESIGN.md token spec files.
expect
Diff-aware AI browser testing — reads the git diff, maps changes to affected pages via the route map, generates a targeted test plan, and executes it via agent-browser (Rust daemon + CDP, ARIA-tree-first) with pass/fail reporting. Use when testing UI changes, verifying PRs before merge, or running regression checks on…
penpot-mcp
Use this skill whenever the user wants to use AI agents to work with Penpot design files via the Penpot MCP Server. Triggers include: using Penpot through an AI agent, design files, design systems, design tokens, Penpot MCP, design-to-code, generating UI from design, auditing a design system, creating…
convert-mobile
Compress the Donahoe Method into mobile-first single-column layouts: thumb-zone CTA placement, Fitts-sized touch targets, mobile reading-pattern adaptation, sticky bottom CTA, and Method-density preservation under 375px width. Use when designing or rebuilding mobile rendering of a sales page, VSL page, lead-magnet…
frontend-ui-engineering
Builds production-quality UIs. Use when building or modifying user-facing interfaces. Use when creating components, implementing layouts, managing state, or when the output needs to look and feel production-quality rather than AI-generated.