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/tyrchen/cursor-rust-rulesWrote 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/tyrchen/cursor-rust-rules/design-patterns)<a href="https://agentmods.dev/rules/tyrchen/cursor-rust-rules/design-patterns"><img src="https://agentmods.dev/badge/rules/tyrchen/cursor-rust-rules/design-patterns/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/tyrchen/cursor-rust-rules/design-patterns"><img src="https://agentmods.dev/badge/rules/tyrchen/cursor-rust-rules/design-patterns.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.05805 |
| Opus 5.5 | $0.00000 | $0.02322 |
| Sonnet 5.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 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.
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.
- 1mo 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
rust-module-refactor
Use when splitting Rust modules, moving tests, tightening visibility, or preserving facades during refactors.
rust-architect
PoolAI — Rust Architect workflow: runtime stack, MSYS2, target/ disk, pre-push checks, docs sync.
table-of-contents-standard
Standard section ordering and TOC format for Verus source files.
arc-deref-pattern
When implementing parallel (Mt) algorithms in Verus, do NOT assume.
wrap-vs-specify
When to use externaltypespecification vs wrapper struct for Verus specs.
core
Core STT/TTS abstraction layer documentation.