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 instructions/dev-lou/pixelpilot/uiux-contributinggit clone --depth 1 https://github.com/dev-lou/PixelPilotWhat 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.00883 | $0.00883 |
| Opus 5 | $0.00441 | $0.00441 |
| Sonnet 5 | $0.00177 | $0.00177 |
| Haiku 4.5 | $0.00088 | $0.00088 |
Grade A, and why
PixelPilot uiux-contributing.instructions.md 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contributing to OpenCode UI/UX 2026 Design System
This guide outlines the process for adding new patterns, components, or rules to the OpenCode UI/UX 2026 Design System. Following these steps ensures consistency, maintainability, and adherence to our established standards.
1. Identify the Right Category
Before creating a new file, determine the most appropriate category for your pattern. The .opencode/rules/ directory contains various categories, such as uiux-components.md, uiux-forms.md, uiux-motion.md, etc. If your pattern doesn't fit an existing category, consider if a new category is truly warranted or if it can be integrated into a broader existing rule.
2. File Naming Conventions
All new rule files should follow the uiux-<category-name>.md or <meta-skill-name>.md convention. For example, a new rule for advanced tables would be uiux-advanced-tables.md. Ensure names are descriptive and concise.
3. Using Design Tokens
Strict adherence to the design token system is paramount. Always use semantic design tokens (e.g., var(--space-4), var(--accent)) instead of raw pixel values or hardcoded colors. Refer to uiux-tokens.md for the complete token architecture and available tokens. This ensures brand consistency and easy theming.
/* GOOD: Using a semantic design token for spacing */
.my-component {
padding: var(--space-4);
background-color: var(--surface);
}
/* BAD: Hardcoded values */
.my-component {
padding: 16px;
background-color: #FFFFFF;
}
4. Updating AGENTS.md
After creating a new rule file, you MUST update AGENTS.md to include it in the RULE FILES table. This ensures that AI agents are aware of the new rule and can load it when relevant. Add an entry with the file name, a brief description of its contents, and when it should be loaded.
| File | Contents | Load when |
|--------------------|----------------------------------------------|--------------------|
| `uiux-new-rule.md` | Guidelines for implementing new UI patterns. | New UI patterns |
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.
- 2d ago First seen · 72 lines · 883 tokens per session scan A c11384db3add
PixelPilot uiux-contributing.instructions.md is an instructions file published in the GitHub repository dev-lou/PixelPilot (2 stars, last pushed 4mo ago), licensed MIT. It adds 883 tokens to every session, about $0.0044 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 instructions, from other repositories
ui-ux-design-pro-skill CLAUDE.md
Instructions for saifyxpro/ui-ux-design-pro-skill, covering project overview, cli commands, full design system generation (markdown output), search across all databases (sub-50ms) and audit ui code quality.
UIX CLAUDE.md
Instructions for Deepractice/UIX, covering uix project rules, design system: lucid ui, colors, forbidden and preferred patterns.
wonder-blocks storybook.instructions.md
Storybook best practices for Wonder Blocks component stories.
wonder-blocks AGENTS.md
Instructions for Khan/wonder-blocks, covering wonder blocks – agentic workflows & storybook mcp, installing the mcp (consumer setup), storybook mcp server, when it’s available and mcp endpoint.
openbridge-webcomponents watch-radial-instruments.instructions.md
Instructions for Ocean-Industries-Concept-Lab/openbridge-webcomponents, covering watch & radial instruments, architecture overview, key principle: logic in watch.ts, instruments stay thin, shared sibling modules and layering & stacking pattern.
oh-my-design CLAUDE.md
Instructions for kwakseongjae/oh-my-design, a project described as: Give your AI coding agent a design system. One command installs 400+ quality-graded company DESIGN.md references + skills into Claude Code, Codex, Cursor, and OpenCode. Free, MIT, zero AI calls.