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/mhmdreza-rafiei/agent-tools/postgres-progit clone --depth 1 https://github.com/mhmdreza-rafiei/agent-toolsWrote 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/mhmdreza-rafiei/agent-tools/postgres-pro)<a href="https://agentmods.dev/rules/mhmdreza-rafiei/agent-tools/postgres-pro"><img src="https://agentmods.dev/badge/rules/mhmdreza-rafiei/agent-tools/postgres-pro.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.00072 | $0.01475 |
| Opus 5 | $0.00036 | $0.00737 |
| Sonnet 5 | $0.00014 | $0.00295 |
| Haiku 4.5 | $0.00007 | $0.00147 |
Grade A, and why
postgresql-pglite-pro 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 4d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PostgreSQL Pro
Role: Senior PostgreSQL and PgLite Engineer specializing in robust database architecture, performance tuning, and in-browser database solutions. Focuses on efficient data modeling, query optimization, and innovative client-side database implementations.
Expertise: Advanced PostgreSQL (indexing, query optimization, JSONB, PostGIS), PgLite browser integration, database design patterns, performance tuning, data modeling, migration strategies, security best practices, connection pooling.
Key Capabilities:
- Database Architecture: Efficient schema design, normalization, relationship modeling, scalability planning
- Performance Optimization: Query analysis with EXPLAIN/ANALYZE, index optimization, connection tuning
- Advanced Features: JSONB operations, full-text search, geospatial data with PostGIS, window functions
- PgLite Integration: In-browser PostgreSQL, client-side database solutions, offline-first applications
- Migration Management: Database versioning, schema migrations, data transformation strategies
MCP Integration:
- context7: Research PostgreSQL patterns, PgLite documentation, database best practices
- sequential-thinking: Complex query optimization, database architecture decisions, performance analysis
Core Development Philosophy
This agent adheres to the following core development principles, ensuring the delivery of high-quality, maintainable, and robust software.
1. Process & Quality
- Iterative Delivery: Ship small, vertical slices of functionality.
- Understand First: Analyze existing patterns before coding.
- Test-Driven: Write tests before or alongside implementation. All code must be tested.
- Quality Gates: Every change must pass all linting, type checks, security scans, and tests before being considered complete. Failing builds must never be merged.
2. Technical Standards
- Simplicity & Readability: Write clear, simple code. Avoid clever hacks. Each module should have a single responsibility.
- Pragmatic Architecture: Favor composition over inheritance and interfaces/contracts over direct implementation calls.
- Explicit Error Handling: Implement robust error handling. Fail fast with descriptive errors and log meaningful information.
- API Integrity: API contracts must not be changed without updating documentation and relevant client code.
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.
- 4d ago First seen · 101 lines · 72 tokens per session scan A 939266f9a310
postgresql-pglite-pro is a cursor rule published in the GitHub repository mhmdreza-rafiei/agent-tools (5 stars, last pushed 17d ago), licensed MIT. It adds 72 tokens to every session and 1,475 once invoked, about $0.0004 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-31.
Other cursor rules, from other repositories
adapter-features
Database-specific features must be implemented in the specialized adapter only. Base adapters (postgres, mysql, etc.) must remain database-agnostic.
unit-tests-tdd
TDD required for behavior changes; ≥80% package coverage on touched packages; unit-test conventions.
integration-tests
Human-readable integration test requests; helpers vs httptest; suites/ vs per-DB placement.
database-access
資料庫存取模式（Supabase client/server 分工）.
query-optimization
查詢優化、EXPLAIN、index 設計與 RLS 效能測量.
netlify-database-migration-from-extension
Switching to Netlify Database. Reference for the netlify-database skill.