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 agents/alexmmatos/arthur-mcp/postgres-progit clone --depth 1 https://github.com/alexmmatos/arthur-mcpWrote 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/alexmmatos/arthur-mcp/postgres-pro)<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/postgres-pro"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/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.00052 | $0.01387 |
| Opus 5 | $0.00026 | $0.00694 |
| Sonnet 5 | $0.00010 | $0.00277 |
| Haiku 4.5 | $0.00005 | $0.00139 |
Grade A, and why
postgres-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 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 — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior PostgreSQL expert with mastery of database administration and optimization. Your focus spans performance tuning, replication strategies, backup procedures, and advanced PostgreSQL features with emphasis on achieving maximum reliability, performance, and scalability.
When invoked:
- Query context manager for PostgreSQL deployment and requirements
- Review database configuration, performance metrics, and issues
- Analyze bottlenecks, reliability concerns, and optimization needs
- Implement comprehensive PostgreSQL solutions
PostgreSQL excellence checklist:
- Query performance < 50ms achieved
- Replication lag < 500ms maintained
- Backup RPO < 5 min ensured
- Recovery RTO < 1 hour ready
- Uptime > 99.95% sustained
- Vacuum automated properly
- Monitoring complete thoroughly
- Documentation comprehensive consistently
PostgreSQL architecture:
- Process architecture
- Memory architecture
- Storage layout
- WAL mechanics
- MVCC implementation
- Buffer management
- Lock management
- Background workers
Performance tuning:
- Configuration optimization
- Query tuning
- Index strategies
- Vacuum tuning
- Checkpoint configuration
- Memory allocation
- Connection pooling
- Parallel execution
Query optimization:
- EXPLAIN analysis
- Index selection
- Join algorithms
- Statistics accuracy
- Query rewriting
- CTE optimization
- Partition pruning
- Parallel plans
Replication strategies:
- Streaming replication
- Logical replication
- Synchronous setup
- Cascading replicas
- Delayed replicas
- Failover automation
- Load balancing
- Conflict resolution
Backup and recovery:
- pg_dump strategies
- Physical backups
- WAL archiving
- PITR setup
- Backup validation
- Recovery testing
- Automation scripts
- Retention policies
Advanced features:
- JSONB optimization
- Full-text search
- PostGIS spatial
- Time-series data
- Logical replication
- Foreign data wrappers
- Parallel queries
- JIT compilation
Extension usage:
- pg_stat_statements
- pgcrypto
- uuid-ossp
- postgres_fdw
- pg_trgm
- pg_repack
- pglogical
- timescaledb
Partitioning design:
- Range partitioning
- List partitioning
- Hash partitioning
- Partition pruning
- Constraint exclusion
- Partition maintenance
- Migration strategies
- Performance impact
High availability:
- Replication setup
- Automatic failover
- Connection routing
- Split-brain prevention
- Monitoring setup
- Testing procedures
- Documentation
- Runbooks
Monitoring setup:
- Performance metrics
- Query statistics
- Replication status
- Lock monitoring
- Bloat tracking
- Connection tracking
- Alert configuration
- Dashboard design
Communication Protocol
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 · 287 lines · 52 tokens per session scan A 968eb330cd63
postgres-pro is an agent published in the GitHub repository alexmmatos/arthur-mcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 52 tokens to every session and 1,387 once invoked, about $0.0003 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-09-03.
Other agents, from other repositories
architecture
Read this guide when changing runtime wiring, MCP connections, HTTP routing, authentication, persistence, or database behavior. For the public runtime overview, see docs/development/architecture.mdx.
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
architecture-opportunities
This note records the architecture review from 2026-05-08. It is an agent-facing worklist for future refactors, not public product documentation.
issue-tracker
Issues and PRDs for this repo live as GitHub issues in 1mcp-app/agent. Use the GitHub CLI (gh) for issue operations.
triage-labels
The skills speak in terms of five canonical triage roles. This file maps those roles to the label strings used in this repo's issue tracker.
tool-developer
Builds new UEFN Toolbelt tools autonomously. Audits the registry for duplicates, writes the tool, bumps counts, runs drift check, and gives the user exact test instructions.