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/chand1012/cursorrulesWrote 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/chand1012/cursorrules/tauri)<a href="https://agentmods.dev/rules/chand1012/cursorrules/tauri"><img src="https://agentmods.dev/badge/rules/chand1012/cursorrules/tauri/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/chand1012/cursorrules/tauri"><img src="https://agentmods.dev/badge/rules/chand1012/cursorrules/tauri.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.01251 |
| Opus 5.5 | $0.00000 | $0.00500 |
| Sonnet 5.5 | $0.00000 | $0.00250 |
| Haiku 4.5 | $0.00000 | $0.00125 |
Grade A, and why
tauri 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tauri 2.0 Best Practices
Project Structure
- Separate Frontend and Backend: Organize your project with a clear distinction between frontend (webview) and backend (Rust) code.
- Frontend Directory: Place frontend code in a
srcdirectory (or a similar convention based on your frontend framework, e.g., React, Vue).- Use subdirectories for route-specific components if using a router (e.g.,
src/routes). - Place shared components in
src/components. - Place utilities and helpers in
src/lib.
- Use subdirectories for route-specific components if using a router (e.g.,
- Backend Directory: Place Rust backend code in the
src-tauridirectory.- Follow Rust’s module system for organizing backend code (e.g.,
src-tauri/src/main.rs,src-tauri/src/lib.rs).
- Follow Rust’s module system for organizing backend code (e.g.,
- Naming Convention: Use lowercase with dashes for directories (e.g.,
components/auth-wizard).
Components
- Efficiency: Design components to minimize resource usage, as Tauri apps run on desktop environments with varying hardware capabilities.
- Backend Interaction: Use Tauri’s API (
invoke) to call Rust backend functions from the frontend. - Error Handling: Implement proper error handling for backend calls to ensure a robust user experience.
- Asynchronous Operations: Consider using Suspense or similar patterns in your frontend framework for handling asynchronous backend interactions.
- File Organization: Place static content (e.g., constants) and interfaces at the end of files for better readability.
Performance
- Asset Optimization: Optimize images and assets by using appropriate formats (e.g., WebP), compressing them, and implementing lazy loading when possible.
- Minimize Frontend Load: Offload heavy computations to the Rust backend instead of the frontend to reduce resource demands.
- State Efficiency: Use efficient state management to avoid unnecessary re-renders in the frontend (e.g., React’s
useMemo,useCallback). - Lazy Loading: Implement lazy loading for non-critical components or features to improve startup time.
- Resource Monitoring: Monitor and optimize the app’s memory and CPU usage, leveraging tools like Tauri’s debugging capabilities.
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 · 75 lines · 0 tokens per session scan A 848ed4ec9a74
tauri is a cursor rule published in the GitHub repository chand1012/cursorrules (13 stars, last pushed 10mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,251 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.