database-implementations

A set of coding rules for building and changing database connectors, which are the parts of an application that communicate with databases.

In plain words
What is it for?
Use it when adding or modifying database support, including connection handling, queries, table lists, and schema inspection.
Why use it?
It keeps different database connectors consistent and helps prevent connection leaks, invalid queries, and unclear errors.

Cursor rule for Cursor

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.

agentmods
npx agentmods add rules/cuongtl1992/mcp-dbs/database-implementations
Clone the repo
git clone --depth 1 https://github.com/cuongtl1992/mcp-dbs

Made for: Cursor.

Per session 550 This file is loaded in full into every session.
When invoked 550 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00550 $0.00550
Opus 5 $0.00275 $0.00275
Sonnet 5 $0.00110 $0.00110
Haiku 4.5 $0.00055 $0.00055

Measured 2d ago against content hash e386a2393f43, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

database-implementations 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 2d 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.

.cursor/rules/database-implementations.mdc · 114 lines

How it starts

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

Database Implementation Rules

When implementing or modifying database connectors, follow these guidelines:

Interface Compliance

All database implementations must fully implement the Database interface:

export interface Database {
  connect(): Promise<void>;
  disconnect(): Promise<void>;
  query(query: string, params?: any[]): Promise<any>;
  execute(query: string, params?: any[]): Promise<void>;
  getTables(): Promise<string[]>;
  getTableSchema(tableName: string): Promise<TableSchema>;
  getSchema(): Promise<SchemaInfo>;
}

Connection Management

  • Always implement proper connection management with explicit connect/disconnect methods
  • Release resources in disconnect methods to prevent memory leaks
  • Validate connection state before executing queries
// ✅ Good
async disconnect(): Promise<void> {
  if (this.pool) {
    await this.pool.end();
    this.pool = null;
  }
}

// ❌ Bad
async disconnect(): Promise<void> {
  await this.pool.end();
}

Error Handling

  • Include informative error messages
  • Properly propagate database-specific errors
  • Use the ensureConnected pattern to check connection state
// ✅ Good
private ensureConnected(): void {
  if (!this.pool) {
    throw new Error('Database not connected. Call connect() first.');
  }
}

async query(query: string, params: any[] = []): Promise<any> {
  this.ensureConnected();
  try {
    const result = await this.pool!.query(query, params);
    return result.rows;
  } catch (error) {
    throw new Error(`Query execution failed: ${error.message}`);
  }
}

// ❌ Bad
async query(query: string, params: any[] = []): Promise<any> {
  return this.pool.query(query, params);
}

Configuration

  • Use typed configuration objects with clear property names
  • Document each configuration property with JSDoc comments
  • Use environment variables as a secondary configuration source
/**
 * Configuration for PostgreSQL database connection
 */
export interface PostgresConfig {
  /**
   * Database host
   */
  host: string;
  
  /**
   * Database port (default: 5432)
   */
  port?: number;
  
  // Other properties...
}

Read the full file on GitHub · 114 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. 2d ago First seen · 114 lines · 550 tokens per session scan A e386a2393f43

Subscribe to this mod's changes

database-implementations is a cursor rule published in the GitHub repository cuongtl1992/mcp-dbs (21 stars, last pushed 1y ago), licensed MIT. It adds 550 tokens to every session, about $0.0028 per session on Opus 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.