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/SaynaAI/saynaWrote 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/saynaai/sayna/rust)<a href="https://agentmods.dev/rules/saynaai/sayna/rust"><img src="https://agentmods.dev/badge/rules/saynaai/sayna/rust/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/saynaai/sayna/rust"><img src="https://agentmods.dev/badge/rules/saynaai/sayna/rust.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.04445 | $0.04445 |
| Opus 5.5 | $0.01778 | $0.01778 |
| Sonnet 5.5 | $0.00889 | $0.00889 |
| Haiku 4.5 | $0.00445 | $0.00445 |
Grade A, and why
rust 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 — 362 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rust Best Practices (2024-2025)
This document outlines a comprehensive set of best practices for Rust development, covering various aspects from code organization to security and tooling. Adhering to these guidelines will help you write idiomatic, efficient, secure, and maintainable Rust code.
Note: This project uses Rust Edition 2024 (released Feb 2025 with Rust 1.85).
1. Code Organization and Structure
1.1. Directory Structure
src/: Contains all the Rust source code.main.rs: The entry point for binary crates.lib.rs: The entry point for library crates.bin/: Contains source files for multiple binary executables within the same project. Each file inbin/will be compiled into a separate executable.modules/orcomponents/: (Optional) For larger projects, group related modules or components into subdirectories. Use descriptive names.tests/: Integration tests. (See Testing section below for more details.)examples/: Example code that demonstrates how to use the library.
benches/: Benchmark tests (usingcriterionor similar).Cargo.toml: Project manifest file.Cargo.lock: Records the exact versions of dependencies used. Do not manually edit..gitignore: Specifies intentionally untracked files that Git should ignore.README.md: Project documentation, including usage instructions, build instructions, and license information.
sayna/ ├── Cargo.toml ├── Cargo.lock ├── src/ │ ├── main.rs # Entry point for a binary crate │ ├── lib.rs # Entry point for a library crate │ ├── modules/ │ │ ├── module_a.rs # A module within the crate │ │ └── module_b.rs # Another module │ └── bin/ │ ├── cli_tool.rs # A separate binary executable │ └── worker.rs # Another binary executable ├── tests/ │ └── integration_test.rs # Integration tests ├── benches/ │ └── my_benchmark.rs # Benchmark tests using Criterion ├── examples/ │ └── example_usage.rs # Example code using the library ├── README.md
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 · 362 lines · 4,445 tokens per session scan A d0daef889f1c
rust is a cursor rule published in the GitHub repository SaynaAI/sayna (314 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 4,445 tokens to every session, about $0.0178 per session on Opus 5.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
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.
spec-fn-naming
Spec function naming conventions.