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/AlphaBitCore/nexus-gatewayWrote 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/alphabitcore/nexus-gateway/design-tokens)<a href="https://agentmods.dev/rules/alphabitcore/nexus-gateway/design-tokens"><img src="https://agentmods.dev/badge/rules/alphabitcore/nexus-gateway/design-tokens.svg" alt="Measured on agentmods" 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.00513 |
| Opus 5 | $0.00000 | $0.00257 |
| Sonnet 5 | $0.00000 | $0.00103 |
| Haiku 4.5 | $0.00000 | $0.00051 |
Grade A, and why
design-tokens 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 7d 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-token strict (binding, theme/mode safety)
You are editing UI code. All visual values (color, background, border, shadow, padding / margin / gap, font-size, font-weight, border-radius, transition, z-index) must be referenced through CSS variables.
Token layers
- Layer 1 raw tokens —
--g-gray-*,--g-space-*,--g-radius-*,--g-shadow-*,--g-transition-*,--g-z-*. Defined inpackages/ui-shared/src/styles/global.css. - Layer 2 semantic tokens —
--color-*,--sidebar-*,--shadow-*,--space-*,--font-size-*,--radius-*,--transition-*,--z-*. Defined inlight.css/dark.cssand flip withdata-theme.
Components consume Layer 2 by default (semantic intent). Drop to Layer 1 only when semantically neutral.
Forbidden
- Hex /
rgb(a)/hsl(a)literals in*.module.css. - Hex /
rgb(a)literals insidestyle={{}}blocks. - Raw numeric
padding: 8/fontSize: 14/borderRadius: 4etc. instyle={{}}.
Three escape hatches
- Recharts colours — must import from
packages/ui-shared/src/theme/chartColors.ts(the single sanctioned hex source). - CSS variable bridges —
style={{ '--foo': dynamicValue }}is fine. - Runtime-computed dimensions —
style={{ paddingLeft: `${level * 20}px` }}is fine.
Anything else needs an explicit user waiver in chat.
Enforcement
npm run check:design-tokens # CI gate
npm run check:design-tokens:hints # migration suggestions when refactoring legacy code
Skipping this rule requires explicit user approval in chat.
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.
- 7d ago First seen · 45 lines · 0 tokens per session scan A f04d4eb5536a
design-tokens is a cursor rule published in the GitHub repository AlphaBitCore/nexus-gateway (23 stars, last pushed 5d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 513 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
cursor.head
Premium keynote-style UI with refined motion. Dark, minimal, cinematic reveals. Trigger words — "premium," "polished," "cinematic," "Apple-like," "keynote," "launch page," "product reveal," "elevate this screen," "audit this UI.".
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.