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/database)<a href="https://agentmods.dev/rules/tyrchen/cursor-rust-rules/database"><img src="https://agentmods.dev/badge/rules/tyrchen/cursor-rust-rules/database/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/database"><img src="https://agentmods.dev/badge/rules/tyrchen/cursor-rust-rules/database.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.03597 |
| Opus 5.5 | $0.00000 | $0.01439 |
| Sonnet 5.5 | $0.00000 | $0.00719 |
| Haiku 4.5 | $0.00000 | $0.00360 |
Grade A, and why
database 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 — 504 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🗄️ RUST DATABASE BEST PRACTICES
TL;DR: Comprehensive guidelines for database access in Rust using SQLx, focusing on type safety, async patterns, and testing strategies.
🔍 DATABASE ARCHITECTURE STRATEGY
graph TD
Start["Database Integration"] --> DBChoice{"Database<br>Type?"}
DBChoice -->|PostgreSQL| Postgres["PostgreSQL with SQLx"]
DBChoice -->|SQLite| SQLite["SQLite with SQLx"]
DBChoice -->|Multiple| MultiDB["Multi-Database Support"]
Postgres --> ConnectionPool["Connection Pool Setup"]
SQLite --> ConnectionPool
MultiDB --> ConnectionPool
ConnectionPool --> Migrations["Database Migrations"]
Migrations --> EntityDesign["Entity Design"]
EntityDesign --> RepositoryPattern["Repository Pattern"]
RepositoryPattern --> QueryPatterns["Query Patterns"]
QueryPatterns --> TypeSafety["Type Safety"]
TypeSafety --> ErrorHandling["Error Handling"]
ErrorHandling --> Testing["Database Testing"]
Testing --> Transactions["Transaction Management"]
Transactions --> Performance["Performance Optimization"]
Performance --> Production["Production Database"]
style Start fill:#4da6ff,stroke:#0066cc,color:white
style ConnectionPool fill:#4dbb5f,stroke:#36873f,color:white
style RepositoryPattern fill:#ffa64d,stroke:#cc7a30,color:white
style Testing fill:#d94dbb,stroke:#a3378a,color:white
🎯 DATABASE LIBRARY SELECTION
SQLx as the Standard
- Always use SQLx - avoid
rusqlite,tokio-postgres, or other lower-level libraries - Support multiple databases through SQLx's unified interface
- Leverage compile-time query checking when possible
- Use async/await patterns for all database operations
# Cargo.toml - SQLx configuration
[dependencies]
sqlx = { version = "0.8", features = [
"chrono",
"postgres",
"runtime-tokio-rustls",
"sqlite",
"uuid"
] }
🔧 QUERY PATTERNS
Use sqlx::query_as Instead of Macros
// ✅ Preferred: Use sqlx::query_as with custom types
#[derive(Debug, Clone, sqlx::FromRow, Serialize, Deserialize)]
#[serde(rename_all = "camelCase")]
pub struct User {
pub id: Uuid,
pub username: String,
pub email: String,
pub created_at: DateTime<Utc>,
pub updated_at: DateTime<Utc>,
pub is_active: bool,
}
impl User {
pub async fn find_by_id(
pool: &PgPool,
id: Uuid
) -> Result<Option<Self>, sqlx::Error> {
sqlx::query_as::<_, User>(
"SELECT id, username, email, created_at, updated_at, is_active
FROM users
WHERE id = $1"
)
.bind(id)
.fetch_optional(pool)
.await
}
pub async fn list_active_users(
pool: &PgPool,
limit: i64,
offset: i64,
) -> Result<Vec<Self>, sqlx::Error> {
sqlx::query_as::<_, User>(
"SELECT id, username, email, created_at, updated_at, is_active
FROM users
WHERE is_active = true
ORDER BY created_at DESC
LIMIT $1 OFFSET $2"
)
.bind(limit)
.bind(offset)
.fetch_all(pool)
.await
}
}
// ❌ Avoid: sqlx::query! macro (compile-time dependencies)
// let result = sqlx::query!("SELECT * FROM users WHERE id = $1", user_id)
// .fetch_one(pool)
// .await?;
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 · 504 lines · 0 tokens per session scan A a9b5f5f80731
database 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 3,597 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
sql-types-imports
Canonical import paths for SQL types.
cursorrules
You are an expert in Solidity, TypeScript, Node.js, postgres, Sqlite3, and Prisma.
neon-python-sdk
Use these rules to manage your Neon projects, branches, databases, and other resources programmatically using the Neon Python SDK.
database-interaction-best-practices
Best practices when interacting with databases in backend Go code.
entity-class-conventions
description: Sets the standards for entity class design including annotations, ID generation strategies, and relationship configurations for database interaction. globs: /src/main/java/com/example/entities/.java.
drizzle
Drizzle ORM best practices for type-safe SQL queries.