rust-rules

rust-rules is a cursor rule for Cursor from beel-collab/presets.dev. It costs 0 tokens per session (1,112 once invoked), scanned A, original, MIT.

A set of file-based instructions for Cursor when working with Rust, a systems programming language. It covers ownership, error handling, asynchronous code, security, performance, and tests, while respecting the project's toolchain and minimum supported version.

In plain words
What is it for?
Use it when writing or reviewing Rust libraries, command-line programs, asynchronous code, error handling, or foreign-function interfaces.
Why use it?
It helps avoid unsafe shortcuts, unnecessary dependency changes, and code that requires a newer Rust version than the project supports. It also encourages errors and unsafe operations to stay explicit.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc). Also seen: mentions Codex; mentions Cursor.

Good fit Use it when writing or reviewing Rust libraries, command-line programs, asynchronous code, error handling, or foreign-function interfaces.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/beel-collab/presets.dev/rust-rules
Install

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.

Clone the repo
git clone --depth 1 https://github.com/beel-collab/presets.dev

Made for: Cursor.

Wrote 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.

agentmods badge for rust-rules

README.md
[![agentmods](https://agentmods.dev/badge/rules/beel-collab/presets.dev/rust-rules/github.svg)](https://agentmods.dev/rules/beel-collab/presets.dev/rust-rules)
Your own site
<a href="https://agentmods.dev/rules/beel-collab/presets.dev/rust-rules"><img src="https://agentmods.dev/badge/rules/beel-collab/presets.dev/rust-rules/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.

agentmods 80×15 button for rust-rules

Your own site · 80×15
<a href="https://agentmods.dev/rules/beel-collab/presets.dev/rust-rules"><img src="https://agentmods.dev/badge/rules/beel-collab/presets.dev/rust-rules.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 1,112 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01112
Opus 5.5 $0.00000 $0.00445
Sonnet 5.5 $0.00000 $0.00222
Haiku 4.5 $0.00000 $0.00111

Measured today against content hash aadaab99fef6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

rust-rules 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 today.

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.

cursor/rust/rust-rules.mdc · 101 lines

How it starts

The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Rust Rules for Cursor: Ownership, Errors and Async

Install

Install the native export at .cursor/rules/rust-rules.mdc. Copy that export, not this catalog file. Catalog fields such as tools and author are for presets.dev. Install one skill file per name. Cursor, GitHub Copilot, Codex, Antigravity CLI, and Devin can all read .agents/skills, so a second copy with the same name collides.

Rust Rules for Cursor: Ownership, Errors and Async

File-scoped Cursor rule for Rust. It attaches when a matching file is in context.

Updated for Rust 1.100.0, Nov 2026

Do not upgrade dependencies or the framework version unless the task asks.

Stay on the rust-toolchain and the MSRV in Cargo.toml. Rust 1.100.0 stabilizes the never type and custom allocators. The 1.99 C-ABI variadics and raw-pointer layout APIs are already stable. Those FFI and layout APIs are not a reason to rewrite safe Rust. Do not raise the MSRV just because 1.100 exists. Read Cargo.toml before you add a crate.

Project shape

A library crate returns Result. A binary's main decides how to exit. Modules follow the existing tree. unsafe lives in the smallest block that needs it, with a comment that states the invariant. Do not use unsafe to avoid the borrow checker.

Prefer borrowing. Clone when the ownership story is actually a copy, and say why if the clone is on a hot path.

Errors

Library code does not unwrap or expect on a path a caller can trigger. expect is for a bug in the program, with a message that explains the broken invariant. Use the project's error type. ? propagates. A match that drops the error and returns a default hides a failure.

Async

An async function is cancel-safe at its await points, or it documents that it is not. Cancel safety is what happens if the future is dropped at an .await. It is separate from which mutex you hold.

Do not hold a std::sync::Mutex or a parking_lot guard across an .await. Those guards are !Send, so the future cannot be spawned on a multi-thread runtime. Holding one also blocks a worker thread and can deadlock. tokio::sync::Mutex is the lock you may hold across .await. A spawned task has a join handle or a structured scope. Blocking work does not run on the async runtime. Use the project's spawn_blocking helper.

Read the full file on GitHub · 101 lines

Changes

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.

  1. today First seen · 101 lines · 0 tokens per session scan A aadaab99fef6

Subscribe to this mod's changes

rust-rules is a cursor rule published in the GitHub repository beel-collab/presets.dev (3 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,112 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-11-13.

Related

rust-rules compared with cursor rules from other repositories

rust-rules next to 6 cursor rules from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
rust-rulesbeel-collab/presets.devCursor rule3yesterdayMITA0Cursor
ponytailDietrichGebert/ponytailCursor rule190k15d agoMITA604Cursor
angular-20angular/angularCursor rule101ktodayMITA0Cursor
dev-standardapache/supersetCursor rule76ktodayApache-2.0A1,147Cursor
prefer-direct-imports-over-module-mocksprisma/ormCursor rule48ktodayApache-2.0A0Cursor
config-validation-and-normalizationprisma/ormCursor rule48ktodayApache-2.0A0Cursor
control-plane-descriptorsprisma/ormCursor rule48ktodayApache-2.0A0Cursor