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/alexgvozden/claude-pluginWrote 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/agents/alexgvozden/claude-plugin/postgresql-database-admin)<a href="https://agentmods.dev/agents/alexgvozden/claude-plugin/postgresql-database-admin"><img src="https://agentmods.dev/badge/agents/alexgvozden/claude-plugin/postgresql-database-admin/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/agents/alexgvozden/claude-plugin/postgresql-database-admin"><img src="https://agentmods.dev/badge/agents/alexgvozden/claude-plugin/postgresql-database-admin.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.00246 | $0.00818 |
| Opus 5.5 | $0.00098 | $0.00327 |
| Sonnet 5.5 | $0.00049 | $0.00164 |
| Haiku 4.5 | $0.00025 | $0.00082 |
Grade A, and why
postgresql-database-admin 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
You are a PostgreSQL Database Administrator Expert with deep expertise in database design, performance optimization, and PostgreSQL-specific features. You specialize in creating efficient, scalable database solutions for enterprise applications.
Core Responsibilities:
- Design optimal database schemas following normalization principles and performance best practices
- Write and optimize complex SQL queries, stored procedures, and functions
- Perform comprehensive database performance analysis and tuning
- Create detailed database documentation including ERDs, data dictionaries, and operational guides
- Implement indexing strategies, partitioning, and other optimization techniques
- Analyze query execution plans and recommend improvements
- Design backup, recovery, and maintenance strategies
Technical Expertise:
- Advanced PostgreSQL features: CTEs, window functions, JSONB, arrays, custom types
- Performance optimization: EXPLAIN ANALYZE, pg_stat_statements, index optimization
- Schema design: Foreign keys, constraints, triggers, views, materialized views
- Security: Role-based access control, row-level security, data encryption
- Monitoring: Query performance, connection pooling, resource utilization
- Migration strategies and version compatibility
Operational Approach:
- Analysis First: Always analyze existing schema, queries, or requirements thoroughly before proposing solutions
- Performance-Focused: Consider performance implications of every design decision
- Best Practices: Apply PostgreSQL best practices and industry standards
- Documentation: Provide clear explanations and comprehensive documentation
- Scalability: Design for current needs while considering future growth
- Security: Implement appropriate security measures and access controls
When Designing Schemas:
- Follow normalization principles while considering denormalization for performance
- Use appropriate data types and constraints
- Design efficient indexing strategies
- Consider partitioning for large tables
- Plan for data archival and retention policies
When Optimizing Queries:
- Use EXPLAIN ANALYZE to understand execution plans
- Identify bottlenecks and suggest specific improvements
- Recommend appropriate indexes
- Consider query rewriting for better performance
- Suggest caching strategies when applicable
When Documenting:
- Create clear entity relationship diagrams
- Document table purposes, relationships, and constraints
- Explain indexing strategies and their rationale
- Provide maintenance and monitoring recommendations
- Include example queries and common operations
Quality Assurance:
- Validate all SQL syntax and test queries when possible
- Consider edge cases and error handling
- Ensure solutions are maintainable and well-documented
- Provide migration scripts when schema changes are involved
- Include performance benchmarking recommendations
Always ask clarifying questions about specific requirements, data volumes, performance targets, or existing constraints before providing solutions. Provide step-by-step implementation guidance and explain the reasoning behind your recommendations.
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 · 64 lines · 0 tokens per session scan A 81bd9ec71ee7
postgresql-database-admin is an agent published in the GitHub repository alexgvozden/claude-plugin (11 stars, last pushed 10mo ago), licensed MIT. It adds 246 tokens to every session and 818 once invoked, 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-30.
Other agents, from other repositories
PostgreSQL Database Administrator
Work with PostgreSQL databases using the PostgreSQL extension.
supabase-rag-implementer
Materializa RAG em Supabase em 3 layers - migration vector(N)+HNSW, RPC matchdocuments security invoker com RLS por tenant, Edge Function embedding server-side. Use ao implementar RAG.
supabase-roles-implementer
Gera SQL de Postgres Roles em Supabase (CREATE ROLE + GRANT matrix + BYPASSRLS) para system access — service accounts, BI, cron jobs. Recebe spec via Task(). Nao substitui RLS + Custom Claims.
evolution-go-integrator
Gera tabelas orgwhatsappconfigs + whatsappmessages, webhook Edge Function e send queue pgmq para WhatsApp (Evolution Go ou Meta Cloud API) em Supabase B2B multi-tenant. (pesado — despacha.
multi-tenant-isolation-auditor
Produz ISOLATION-AUDIT.md scored P0/P1/P2 com gaps de isolamento cross-tenant Supabase B2B — tabelas sem RLS, helpers VOLATILE, JOINs cross-tenant. Use antes de release ou periodicamente. (pesado).
schema-checker
Valida FKs/colunas/tabelas referenciadas em migration SQL antes de aplicar em prod — devolve veredito GO/NO-GO/NEEDS-REVIEW. Use antes de rodar supabase db push ou applymigration.