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.
npx agentmods add rules/secondlifes/delphi-expert/postgresql-patternsgit clone --depth 1 https://github.com/SecondLifes/delphi-expertWrote 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/secondlifes/delphi-expert/postgresql-patterns)<a href="https://agentmods.dev/rules/secondlifes/delphi-expert/postgresql-patterns"><img src="https://agentmods.dev/badge/rules/secondlifes/delphi-expert/postgresql-patterns.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.01185 |
| Opus 5 | $0.00000 | $0.00593 |
| Sonnet 5 | $0.00000 | $0.00237 |
| Haiku 4.5 | $0.00000 | $0.00119 |
Grade A, and why
postgresql-patterns 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 today.
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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PostgreSQL Database — Rules
Use these rules when developing with PostgreSQL database via FireDAC.
Connection Required
{ Configuração base }
FConnection.DriverName := 'PG';
FConnection.Params.Values['Server'] := 'localhost';
FConnection.Params.Values['Port'] := '5432';
FConnection.Params.Database := 'meubanco';
FConnection.Params.UserName := 'postgres';
FConnection.Params.Password := 'senha';
FConnection.Params.Values['CharacterSet'] := 'UTF8';
Auto-Increment
| Approach | Version | Example |
|---|---|---|
SERIAL |
All | Legacy — creates implicit sequence |
BIGSERIAL |
All | Legacy — 64-bit |
GENERATED ALWAYS AS IDENTITY |
PG 10+ | ✅ Modern — SQL Standard |
GENERATED BY DEFAULT AS IDENTITY |
PG 10+ | Allows manual override |
nextval('seq') |
All | Manual sequence |
RETURNING — Same Rule as Firebird
//❌ ExecSQL loses the returned value!
LQuery.SQL.Text := 'INSERT INTO ... RETURNING id';
LQuery.ExecSQL;
//✅ Open to receive RETURNING
LQuery.SQL.Text := 'INSERT INTO ... RETURNING id';
LQuery.Open;
LId := LQuery.FieldByName('id').AsInteger;
UPSERT — INSERT ... ON CONFLICT
LQuery.SQL.Text :=
'INSERT INTO customers (cpf, name, email) ' +
'VALUES (:cpf, :name, :email) ' +
'ON CONFLICT (cpf) DO UPDATE SET ' +
' name = EXCLUDED.name, email = EXCLUDED.email ' +
'RETURNING id';
LQuery.Open;
JSONB — Semi-Structured Data
{ Gravar JSONB }
LQuery.ParamByName('settings').AsString := '{"theme":"dark"}';
{ Cast necessário no SQL: :param::jsonb }
{ Ler campo JSONB }
LQuery.SQL.Text := 'SELECT settings->>''theme'' FROM ... WHERE id = :id';
Functions and Procedures
| Type | Delphi Call |
|---|---|
| Scalar function | SELECT fn_nome(:param) + Open |
| Function RETURNS TABLE | SELECT * FROM fn_nome(:param) + Open |
| Procedure (PG 11+) | CALL sp_nome(:param) + ExecSQL |
Transactions
{ Transação explícita }
FConnection.StartTransaction;
try
FRepoA.Insert(LObjA);
FRepoB.Insert(LObjB);
FConnection.Commit;
except
FConnection.Rollback;
raise;
end;
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.
- today First seen · 159 lines · 0 tokens per session scan A a3eb942f2b3c
postgresql-patterns is a cursor rule published in the GitHub repository SecondLifes/delphi-expert (3 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,185 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-09-03.
Other cursor rules, from other repositories
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.
aws-rds-best-practices
AWS RDS PostgreSQL best practices - database configuration, connection management, authentication, backup, and performance optimization standards.
database
Database rules — apply when working with database schemas, queries, migrations, or ORM models.
database
Cursor rule "database" from ItamarZand88/awesome-agent-conventions, covering database best practices, prisma setup, prisma models, prisma queries and supabase setup.