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 rules/superplanehq/superplane/ui-shadcn-formsgit clone --depth 1 https://github.com/superplanehq/superplaneWhat 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.00000 | $0.00352 |
| Opus 5 | $0.00000 | $0.00176 |
| Sonnet 5 | $0.00000 | $0.00070 |
| Haiku 4.5 | $0.00000 | $0.00035 |
Grade A, and why
ui-shadcn-forms 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 3d 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
UI: shadcn for Forms and Components
Forms — always use shadcn
- All form UI must use components from
@/components/ui(this project's shadcn primitives). - Use
Input,Label,Select,SelectContent,SelectItem,SelectTrigger,SelectValue,Textarea,Checkbox,Switch,Buttonfrom@/components/ui— do not use raw<input>,<select>,<textarea>, or ad‑hoc form controls when an equivalent exists in@/components/ui. - Pair inputs with
Labeland properhtmlFor/idfor accessibility. - For dialogs/modals that contain forms, use
Dialog,DialogContent,DialogHeader,DialogTitle,DialogDescription,DialogFooterfrom@/components/ui.
New patterns — check shadcn first
- Before adding a new UI element or pattern, check whether
web_src/src/components/ui/already provides a suitable component (e.g. button, input, label, select, dialog, tabs, tooltip, badge, separator, scroll-area, command, slider, textarea). - Prefer composing or customizing an existing shadcn component over building a custom component from scratch.
- Only introduce a new custom component when no existing
@/components/ui(or other design-system) component fits the use case.
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.
- 3d ago First seen · 23 lines · 0 tokens per session scan A 32e567e69d55
ui-shadcn-forms is a cursor rule published in the GitHub repository superplanehq/superplane (5,700 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 352 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-30.
Other cursor rules, from other repositories
css-styling
CSS architecture, tokens, and styling rules for this Docusaurus site. Apply when creating or modifying components, styles, layouts, or any UI-facing code.
codex-premium-website-skills
Apply Codex Skills standards to frontend, website, motion, accessibility, QA, agent reasoning, and handoff work.
ui-components
USE WHEN: Building UI components, structuring layouts, and applying styles using Tailwind CSS.
frontend-architecture
Vite + React SPA architecture - directory layout, providers, bundle splitting. Tailwind styling in tailwind.mdc.
css-render-blocking-diagnosis
Cursor rule "css-render-blocking-diagnosis" from adobecom/da-express-milo, covering css render-blocking diagnosis & resolution, critical learning from 98 pagespeed achievement, primary diagnostic protocol, step 1: css blocking symptom recognition and step 2: css loading sequence audit.
z-index
Z-index layering conventions for consistent stacking.