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/mohtashammurshid/getdesign/dependenciesgit clone --depth 1 https://github.com/MohtashamMurshid/getdesignWrote 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/mohtashammurshid/getdesign/dependencies)<a href="https://agentmods.dev/rules/mohtashammurshid/getdesign/dependencies"><img src="https://agentmods.dev/badge/rules/mohtashammurshid/getdesign/dependencies.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 | $0.00260 | $0.00260 |
| Opus 5 | $0.00130 | $0.00130 |
| Sonnet 5 | $0.00052 | $0.00052 |
| Haiku 4.5 | $0.00026 | $0.00026 |
Grade A, and why
dependencies 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 5d 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
Dependency Management
- Use
bun add <pkg>/bun add -d <pkg>/bun add -D <pkg>to add deps. Never hand-editpackage.jsondependencies/devDependencies. - In workspaces, add deps to a specific package with
bun add <pkg> --filter <pkgName>orcd <pkg-dir> && bun add <pkg>. - Workspace links use
"workspace:*"; add them viabun add <internal-pkg>@workspace:*. - Always use Zod v4 (
zod@^4). Do not installzod@3. - Use
bun install(notnpm i/pnpm i/yarn) at the repo root. - After installing, commit
bun.lock(notbun.lockb).
Examples
# Root dev dep
bun add -d turbo typescript
# Scoped to a workspace package
bun add zod --filter @getdesign/types
# Workspace link
bun add @getdesign/types@workspace:* --filter @getdesign/tools
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.
- 5d ago First seen · 27 lines · 260 tokens per session scan A 9f643d09f161
dependencies is a cursor rule published in the GitHub repository MohtashamMurshid/getdesign (48 stars, last pushed 6d ago), licensed MIT. It adds 260 tokens to every session, about $0.0013 per session on Opus 5. 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
trigger.advanced-tasks
Comprehensive rules to help you write advanced Trigger.dev tasks.
beta
Convert .cursor/rules into a standardized AGENTS.md file.
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.
family-instance-domain-actions
Family instance domain action implementation patterns.