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/tyrchen/cursor-rust-rules/design-patternsgit clone --depth 1 https://github.com/tyrchen/cursor-rust-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.05805 |
| Opus 5 | $0.00000 | $0.02903 |
| Sonnet 5 | $0.00000 | $0.01161 |
| Haiku 4.5 | $0.00000 | $0.00581 |
Grade A, and why
design-patterns 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.
How it starts
The opening of the file, as written. The whole thing — 874 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🎭 RUST DESIGN PATTERNS
TL;DR: Essential design patterns for Rust applications, focusing on idiomatic solutions that leverage Rust's ownership system and zero-cost abstractions.
🔍 DESIGN PATTERN SELECTION STRATEGY
graph TD
Start["Design Challenge"] --> ProblemType{"Problem<br>Category?"}
ProblemType -->|Object Creation| Creational["Creational Patterns"]
ProblemType -->|Object Behavior| Behavioral["Behavioral Patterns"]
ProblemType -->|Object Structure| Structural["Structural Patterns"]
ProblemType -->|Concurrency| ConcurrencyP["Concurrency Patterns"]
Creational --> BuilderCheck{"Complex<br>Configuration?"}
Creational --> FactoryCheck{"Multiple<br>Implementations?"}
BuilderCheck -->|Yes| TypeStateBuilder["Type-State Builder"]
FactoryCheck -->|Yes| AbstractFactory["Abstract Factory"]
Behavioral --> StrategyCheck{"Runtime Algorithm<br>Selection?"}
Behavioral --> CommandCheck{"Undo/Redo<br>Required?"}
Behavioral --> ObserverCheck{"Event-Driven<br>Architecture?"}
StrategyCheck -->|Yes| StrategyPattern["Strategy Pattern"]
CommandCheck -->|Yes| CommandPattern["Command Pattern"]
ObserverCheck -->|Yes| ObserverPattern["Observer Pattern"]
Structural --> AdapterCheck{"External API<br>Integration?"}
Structural --> DecoratorCheck{"Cross-Cutting<br>Concerns?"}
AdapterCheck -->|Yes| AdapterPattern["Adapter Pattern"]
DecoratorCheck -->|Yes| DecoratorPattern["Decorator Pattern"]
ConcurrencyP --> ActorCheck{"Isolated State<br>Management?"}
ConcurrencyP --> PipelineCheck{"Data Pipeline<br>Processing?"}
ActorCheck -->|Yes| ActorPattern["Actor Pattern"]
PipelineCheck -->|Yes| PipelinePattern["Pipeline Pattern"]
TypeStateBuilder --> Implementation["Implementation"]
AbstractFactory --> Implementation
StrategyPattern --> Implementation
CommandPattern --> Implementation
ObserverPattern --> Implementation
AdapterPattern --> Implementation
DecoratorPattern --> Implementation
ActorPattern --> Implementation
PipelinePattern --> Implementation
style Start fill:#4da6ff,stroke:#0066cc,color:white
style Creational fill:#4dbb5f,stroke:#36873f,color:white
style Behavioral fill:#ffa64d,stroke:#cc7a30,color:white
style Structural fill:#d94dbb,stroke:#a3378a,color:white
style ConcurrencyP fill:#9d4dbb,stroke:#7a3a8a,color:white
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 · 874 lines · 0 tokens per session scan A ff237d97be20
design-patterns is a cursor rule published in the GitHub repository tyrchen/cursor-rust-rules (27 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 5,805 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.