Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/tyrchen/cursor-rust-rulesnpx agentmods add rules/tyrchen/cursor-rust-rules/workspaceWrote 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/workspace)<a href="https://agentmods.dev/rules/tyrchen/cursor-rust-rules/workspace"><img src="https://agentmods.dev/badge/rules/tyrchen/cursor-rust-rules/workspace/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/workspace"><img src="https://agentmods.dev/badge/rules/tyrchen/cursor-rust-rules/workspace.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.09549 |
| Opus 5.5 | $0.00000 | $0.03820 |
| Sonnet 5.5 | $0.00000 | $0.01910 |
| Haiku 4.5 | $0.00000 | $0.00955 |
Grade A, and why
workspace 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 — 1,318 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🏢 MULTI-CRATE WORKSPACE STRUCTURE
TL;DR: Guidelines for organizing complex Rust projects using workspace architecture with multiple crates, clear subsystem boundaries, and domain-driven design principles.
🔍 WORKSPACE ARCHITECTURE STRATEGY
graph TD
Start["Complex Project"] --> ArchType{"Architecture<br>Pattern?"}
ArchType -->|Domain-Driven| DomainArch["Domain-Based Architecture"]
ArchType -->|Service-Oriented| ServiceArch["Service-Based Architecture"]
ArchType -->|Layered| LayeredArch["Layered Architecture"]
DomainArch --> DomainCrates["Domain-Specific Crates"]
ServiceArch --> ServiceCrates["Service-Specific Crates"]
LayeredArch --> LayerCrates["Layer-Specific Crates"]
DomainCrates --> SharedInfra["Shared Infrastructure"]
ServiceCrates --> SharedInfra
LayerCrates --> SharedInfra
SharedInfra --> WorkspaceDeps["Workspace Dependencies"]
WorkspaceDeps --> CrateOrganization["Crate Organization"]
CrateOrganization --> IntegrationTesting["Integration Testing"]
IntegrationTesting --> BuildOptimization["Build Optimization"]
BuildOptimization --> Documentation["Workspace Documentation"]
Documentation --> Production["Production Workspace"]
style Start fill:#4da6ff,stroke:#0066cc,color:white
style DomainArch fill:#4dbb5f,stroke:#36873f,color:white
style ServiceArch fill:#ffa64d,stroke:#cc7a30,color:white
style LayeredArch fill:#d94dbb,stroke:#a3378a,color:white
🏗️ SERVICE-ORIENTED WORKSPACE ARCHITECTURE
graph TD
Workspace["Service Platform Workspace"] --> Shared["Shared Infrastructure"]
Workspace --> CoreServices["Core Services"]
Workspace --> BusinessServices["Business Services"]
Workspace --> PlatformServices["Platform Services"]
Shared --> SharedTypes["shared-types<br/>(domain primitives)"]
Shared --> SharedConfig["shared-config<br/>(configuration)"]
Shared --> SharedObservability["shared-observability<br/>(metrics & tracing)"]
CoreServices --> ServiceCore["service-core<br/>(business logic)"]
CoreServices --> ServiceApi["service-api<br/>(HTTP handlers)"]
CoreServices --> ServiceWorker["service-worker<br/>(background jobs)"]
BusinessServices --> BusinessCore["business-core<br/>(domain logic)"]
BusinessServices --> BusinessApi["business-api<br/>(API endpoints)"]
BusinessServices --> BusinessProcessor["business-processor<br/>(workflow engine)"]
PlatformServices --> Gateway["gateway<br/>(API gateway)"]
PlatformServices --> AdminPanel["admin-panel<br/>(administration)"]
PlatformServices --> HealthMonitor["health-monitor<br/>(monitoring)"]
style Workspace fill:#4da6ff,stroke:#0066cc,color:white
style Shared fill:#4dbb5f,stroke:#36873f,color:white
style CoreServices fill:#ffa64d,stroke:#cc7a30,color:white
style BusinessServices fill:#d94dbb,stroke:#a3378a,color:white
style PlatformServices fill:#9b59b6,stroke:#7d4796,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 · 1,318 lines · 0 tokens per session scan A 05becb32e774
workspace 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 9,549 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
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.