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/harshii0509/designstack/ds-design-contextgit clone --depth 1 https://github.com/harshii0509/designStackWhat 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.00387 |
| Opus 5 | $0.00000 | $0.00193 |
| Sonnet 5 | $0.00000 | $0.00077 |
| Haiku 4.5 | $0.00000 | $0.00039 |
Grade A, and why
ds-design-context 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.
What it actually says
designStack — Design Bible Context
Read design/DESIGN-BIBLE.md before making any changes to files matched by this rule.
The Design Bible contains:
- Your exact brand colors (hex codes)
- Your font families and type scale
- Your spacing system (base unit and scale)
- Your border radius rules
- How your buttons, cards, inputs, and navigation should look
- The feeling and audience for this product
Apply every rule from the Design Bible when:
- Writing or editing CSS / Tailwind classes
- Creating or modifying components
- Choosing colors, font sizes, or spacing values
- Reviewing whether a design looks right
If a change you're making conflicts with the Design Bible, say so before making it:
"The Design Bible says primary buttons should use
[value], but you're asking me to use[other value]. Want me to update the Bible, or follow the existing rule here?"
If you add a new component or pattern not yet in the Design Bible, suggest adding it:
"This is a new pattern — want me to add the rules for it to your Design Bible so it stays consistent?"
From designStack — run /ds:context in Claude Code to refresh these rules.
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 · 40 lines · 0 tokens per session scan A c754750fa831
ds-design-context is a cursor rule published in the GitHub repository harshii0509/designStack (13 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 387 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
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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.