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.
git clone --depth 1 https://github.com/webhook-co/webhookWrote 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/rules/webhook-co/webhook/design-ux)<a href="https://agentmods.dev/rules/webhook-co/webhook/design-ux"><img src="https://agentmods.dev/badge/rules/webhook-co/webhook/design-ux/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/webhook-co/webhook/design-ux"><img src="https://agentmods.dev/badge/rules/webhook-co/webhook/design-ux.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00340 |
| Opus 5.5 | $0.00000 | $0.00136 |
| Sonnet 5.5 | $0.00000 | $0.00068 |
| Haiku 4.5 | $0.00000 | $0.00034 |
Grade A, and why
design-ux 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 1mo 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.
What it actually says
Design & UX (web surfaces)
- Accessibility is a requirement, not a polish pass. Target WCAG 2.2 AA: semantic HTML, labeled controls, visible focus states, keyboard operability for every interaction, and sufficient color contrast. Don't ship interactive elements that only work with a mouse.
- Use the design system / tokens. Style via the shared tokens (color, spacing, typography, radius) — no hardcoded hex values or one-off magic numbers. New patterns go into the system, not into a single component.
- Sentence case for headings, buttons, and labels. Brand names stay lowercase (
webhook.co,wbhk.my). UI copy follows thewriting-voicerule: clear, developer-peer, quietly opinionated. - Respect user preferences: honor
prefers-reduced-motion, support theming where it's offered (the dashboard and the marketing site are both light/dark, defaulting to dark with a toggle to light), and don't trap focus or autoplay motion. - States are part of the design. Always handle loading, empty, error, and permission-denied states — empty states should teach the next action. Inspection/replay views must stay fast and legible with large payloads.
- Private-by-default in the UI too: never imply something is shared/public unless the user explicitly made it so; make sharing affordances explicit and reversible.
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.
- 1mo ago First seen · 25 lines · 0 tokens per session scan A b01522f95b71
design-ux is a cursor rule published in the GitHub repository webhook-co/webhook (0 stars, last pushed 5d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 340 tokens. 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 cursor rules, from other repositories
design-prompts
Starting directions for redesigning or creating a theme.
ui-and-styling-rule
Guidelines for UI and styling, focusing on Tailwind CSS and Shaden UI best practices.
hatch3r-ux-states-and-flows
Four-state surface contract (loading/empty/error/partial), user-flow decomposition before implementation, and microcopy + tone discipline for end-user UIs.
hatch3r-accessibility-standards
Accessibility standards covering WCAG 2.2 AA compliance, keyboard navigation, screen readers, and ARIA patterns.
hatch3r-component-conventions
Component structure, styling tokens, loading/error/empty states, form validation timing, and accessible label patterns for Vue, React, and JSX.
hatch3r-theming
Theming, dark mode, and color system conventions for the project.