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/cuongtl1992/mcp-dbsWrote 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/cuongtl1992/mcp-dbs/database-implementations)<a href="https://agentmods.dev/rules/cuongtl1992/mcp-dbs/database-implementations"><img src="https://agentmods.dev/badge/rules/cuongtl1992/mcp-dbs/database-implementations/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/cuongtl1992/mcp-dbs/database-implementations"><img src="https://agentmods.dev/badge/rules/cuongtl1992/mcp-dbs/database-implementations.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.00550 | $0.00550 |
| Opus 5.5 | $0.00220 | $0.00220 |
| Sonnet 5.5 | $0.00110 | $0.00110 |
| Haiku 4.5 | $0.00055 | $0.00055 |
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 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 — 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...
}
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 · 114 lines · 550 tokens per session scan A e386a2393f43
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.0022 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
as-contract-cast-smell
// ❌ WRONG — bypasses the family ContractSerializer seam const contract = JSON.parse(raw) as Contract; const contract = JSON.parse(raw) as Contract .
no-backward-compatibility
Do not add backward-compatibility shims or migration scaffolding.
postgresql
This guide defines the definitive best practices for writing clean, performant, and maintainable PostgreSQL SQL, focusing on modern conventions and avoiding common pitfalls.
ehs-ims-conventions
EHS IMS app — RBAC, data layer, tRPC, migrations, AI boundaries.
sync-timedb-archive-janitor-contract
Day-close / cold-path worker contracts for synctimedb (A invariants; B tick coordinator retired).
schema
Scalable and secure schema design patterns for relational databases, NoSQL, and APIs. / TR: İlişkisel veri tabanları, NoSQL ve API'ler için ölçeklenebilir ve güvenli şema tasarım kalıpları.