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/harshii0509/designStackWrote 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/harshii0509/designstack/ds-design-context)<a href="https://agentmods.dev/rules/harshii0509/designstack/ds-design-context"><img src="https://agentmods.dev/badge/rules/harshii0509/designstack/ds-design-context/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/harshii0509/designstack/ds-design-context"><img src="https://agentmods.dev/badge/rules/harshii0509/designstack/ds-design-context.svg" alt="Reviewed on agentmods" width="80" 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.00387 |
| Opus 5.5 | $0.00000 | $0.00155 |
| Sonnet 5.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 1mo 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.
- 1mo 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 4mo 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
explorer-interface-brief
Use when asked to design the interface for an interactive 3D explorer, plan a UI for exploring a 3D model of a topic, or write an image-model prompt for a 3D learning app mock-up. Produces, from a topic, the UI design brief (audience, layout, panels, interactions, label style, colour palette, accessibility) and an…
prototype-previewer
Build interactive prototype reviewers with synced review notes and Figma capture pages.
figma-performance
Handling large documents efficiently in the Plugin API.
ant-design
A set of guidelines for using Ant Design, a collection of ready-made interface components, in React applications. It covers code organization, performance, security, testing, and common mistakes.
7-day-nextjs-web-design-cursor
A seven-day design workflow for web products that will be built in Next.js.
clone-ai
Site Clone AI — website klonlama pipeline kuralları.