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/kleosr/kleosrulesWrote 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/kleosr/kleosrules/postgres)<a href="https://agentmods.dev/rules/kleosr/kleosrules/postgres"><img src="https://agentmods.dev/badge/rules/kleosr/kleosrules/postgres/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/kleosr/kleosrules/postgres"><img src="https://agentmods.dev/badge/rules/kleosr/kleosrules/postgres.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.00261 | $0.00261 |
| Opus 5.5 | $0.00104 | $0.00104 |
| Sonnet 5.5 | $0.00052 | $0.00052 |
| Haiku 4.5 | $0.00026 | $0.00026 |
Grade A, and why
postgres 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.
What it actually says
Postgres
Confirm the Postgres engine, not SQLite or MySQL; a Prisma provider must be postgres. Composable with supabase.mdc: when the repo uses Supabase Postgres, apply both (generic SQL here, RLS/auth/pooler there).
Hard
- Parameterized SQL only. No string-concatenated queries.
- Migrations are forward-only, named, and live in the repo's existing folder. No drive-by schema in app code. Each migration still needs a recovery strategy, lock-impact review, and compatibility plan. Never run production queries to "verify" without approval.
- Performance indexes need a measured benefit: run a representative
EXPLAIN(plan only) on representative data. Constraint-supporting indexes follow integrity requirements, not a perf plan.EXPLAIN ANALYZEexecutes the statement — never on production writes without approval. Indexes cost writes and storage. - Do not invent RLS or
auth.uid()unless this repo already uses that model.
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 Changed · -1 lines · +261 tokens per session e5a264bb58a0
- 1mo ago Changed · -4 lines 6ab922a1fe5e
- 1mo ago Changed a75736d0495f
- 1mo ago Changed · -3 lines 5e4339e12447
- 1mo ago Changed · -2 lines fe96a6157464
- 1mo ago First seen · 26 lines · 0 tokens per session scan A dc0755c357ac
postgres is a cursor rule published in the GitHub repository kleosr/kleosrules (0 stars, last pushed 1mo ago), licensed MIT. It adds 261 tokens to every session, about $0.0010 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-31.
Other cursor rules, from other repositories
30-database-postgres
PostgreSQL and persistence rules.
postgresql
PostgreSQL: advanced SQL, performance, extensions.
sql-rls-policies
Supabase Postgres SQL RLS Row Level Security Guide.
sql-format
Supabase Postgres SQL Style Guide.
sql-functions
Supabase Postgres SQL Function Guide.
sql-migrations
Supabase Postgres SQL Migration Guide.