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 instructions/gldc/mcp-postgres/agents-mdgit clone --depth 1 https://github.com/gldc/mcp-postgresWhat 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.00628 | $0.00628 |
| Opus 5 | $0.00314 | $0.00314 |
| Sonnet 5 | $0.00126 | $0.00126 |
| Haiku 4.5 | $0.00063 | $0.00063 |
Grade A, and why
mcp-postgres AGENTS.md 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 2d 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Concise guidance for contributing to the PostgreSQL MCP server in this repo.
Project Structure & Module Organization
- Root:
postgres_server.py(FastMCP server and tools),README.md,requirements.txt,smithery.yaml. - Tests:
tests/test_tools.py(unit),tests/test_integration.py(requires DB). - Config:
.env.example,permissions.yaml.example,railway.toml,smithery.yaml.
Build, Test, and Development Commands
- Create env:
python -m venv .venv && source .venv/bin/activate - Install runtime deps:
pip install -r requirements.txt - Install test deps:
pip install -r dev-requirements.txt - Run server (stdio):
python postgres_server.py --conn "postgresql://user:pass@host:5432/db" - Run server (HTTP):
python postgres_server.py --transport streamable-http --host 127.0.0.1 --port 8000 - Run tests:
pytest -q - Lint:
ruff check .
Coding Style & Naming Conventions
- Python 3.10+, PEP 8, 4-space indent; type hints and short docstrings.
- Names: functions/vars
snake_case; classesPascalCase; MCP tool names shortsnake_case. - Logging: use the module
logger; avoid PII.
Testing Guidelines
- Framework:
pytest+pytest-asynciowith files intests/namedtest_*.py. - No-DSN behavior is required: without
DATABASE_URL, tools must return friendly empty/notice results. - Integration tests are skipped unless
DATABASE_URLis set.
Tools & Resources
- Tools:
query,list_schemas,list_tables,describe_table,get_foreign_keys,find_relationships,server_info,db_identity. - Resources:
table://{schema}/{table}— reads up to 100 rows. - Prompts:
write_safe_select,explain_plan_tips.
Commit & Pull Request Guidelines
- Commits: conventional style (
feat:,fix:,chore:,docs:), imperative and concise. - PRs: include purpose/scope, before/after behavior, example commands/queries, and config changes.
- Do not commit secrets;
.envand credentials are ignored by.gitignore.
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.
- 2d ago First seen · 44 lines · 628 tokens per session scan A 9df4ffe63475
mcp-postgres AGENTS.md is an instructions file published in the GitHub repository gldc/mcp-postgres (15 stars, last pushed 6mo ago), licensed MIT. It adds 628 tokens to every session, about $0.0031 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-30.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
buildNext
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
Instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain AGENTS.md
Instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.