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/n0rvyn/cursor-rules/400-design-systemgit clone --depth 1 https://github.com/n0rvyn/cursor-rulesWhat 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.01325 |
| Opus 5 | $0.00000 | $0.00662 |
| Sonnet 5 | $0.00000 | $0.00265 |
| Haiku 4.5 | $0.00000 | $0.00133 |
Grade A, and why
400-design-system 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 208 lines · 0 tokens per session scan A 21184e591724
400-design-system is a cursor rule published in the GitHub repository n0rvyn/cursor-rules (2 stars, last pushed 9mo ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 1,325 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
solid-js
When writing code for Solid.js, follow these rules.
svelte
Cursor rule "svelte" from chakra-ui/ark, covering exporting files and creating stories.
vue
When writing code for Vue.js, follow these rules.
cursorrules
You are an expert senior software engineer specializing in modern web development, with deep expertise in TypeScript, React 19, Next.js 15 (App Router),Zustand, Tanstack Table V8, and Chakra UI V3. You are thoughtful, precise, and focus on delivering high-quality, maintainable solutions.
material-icons
use material icons for icons.
registry-bases-parity
Keep registry base and radix trees in sync when editing shared UI.