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/lacymorrow/paperclip-hubWrote 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/lacymorrow/paperclip-hub/ui-ux)<a href="https://agentmods.dev/rules/lacymorrow/paperclip-hub/ui-ux"><img src="https://agentmods.dev/badge/rules/lacymorrow/paperclip-hub/ui-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/lacymorrow/paperclip-hub/ui-ux"><img src="https://agentmods.dev/badge/rules/lacymorrow/paperclip-hub/ui-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.00421 |
| Opus 5.5 | $0.00000 | $0.00168 |
| Sonnet 5.5 | $0.00000 | $0.00084 |
| Haiku 4.5 | $0.00000 | $0.00042 |
Grade A, and why
ui-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 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.
What it actually says
UI/UX Design Guidelines
Component Library
- Use Shadcn/UI components for consistency
- Follow component documentation
- Maintain design system
- Customize thoughtfully
- Document modifications
- Keep components accessible
- Test all variants
Styling
- Use Tailwind CSS for styling
- Follow responsive design principles
- Use consistent spacing
- Maintain color system
- Follow typography scale
- Keep styles maintainable
- Document custom styles
Layout
- Use responsive layouts
- Implement proper spacing
- Follow grid system
- Consider mobile first
- Handle breakpoints properly
- Test all screen sizes
- Document layout patterns
Forms
- Use proper validation
- Provide clear feedback
- Handle errors gracefully
- Show loading states
- Support keyboard navigation
- Maintain accessibility
- Document form patterns
Navigation
- Clear navigation structure
- Consistent patterns
- Handle state changes
- Show active states
- Support keyboard nav
- Consider mobile nav
- Document nav patterns
Interactions
- Clear feedback
- Consistent behavior
- Handle loading states
- Show error states
- Support touch devices
- Test all interactions
- Document patterns
Accessibility
- Follow WCAG guidelines
- Support screen readers
- Handle keyboard nav
- Provide alt text
- Use semantic HTML
- Test accessibility
- Document requirements
Performance
- Optimize images
- Handle loading states
- Minimize layout shifts
- Use proper caching
- Monitor performance
- Regular audits
- Document optimizations
Responsive Design
- Mobile-first approach
- Handle breakpoints
- Test all devices
- Consider orientation
- Handle touch input
- Document patterns
- Regular testing
Documentation
- Document components
- Maintain style guide
- Document patterns
- Keep examples updated
- Share best practices
- Regular reviews
- Version control
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 · 97 lines · 421 tokens per session scan A abc09a26fd73
ui-ux is a cursor rule published in the GitHub repository lacymorrow/paperclip-hub (15 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 421 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-11-10.
ui-ux compared with cursor rules from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| ui-uxlacymorrow/paperclip-hub | Cursor rule | 15 | yesterday | MIT | A | 0 | Cursor |
| codex-premium-website-skillsTheGoat395/Codex-Skills | Cursor rule | 137 | 20d ago | MIT | A | 0 | Cursor |
| ui-design-systemkrivoox/agent-stack-template | Cursor rule | 30 | 1mo ago | MIT | A | 0 | Cursor |
| uiuseshape/Shape | Cursor rule | 34 | yesterday | none | A | 0 | Cursor |
| ui-and-styling-rulesWebDevPeterGriffin/The-VibeCode-Bible | Cursor rule | 42 | 7d ago | none | A | 66 | Cursor |
| ui-and-styling-ruleWebDevPeterGriffin/The-VibeCode-Bible | Cursor rule | 42 | 7d ago | none | A | 67 | Cursor |
| ui-componentsFluroAsh/nextjs-mdx-portfolio | Cursor rule | 2 | yesterday | none | A | 3 | Cursor |