What is postgres-mcp-go AGENTS.md?

A set of contribution rules for the postgres-mcp-go Go repository. The project provides an MCP server that connects tools to PostgreSQL, a relational database system.

Use it when adding Go packages or commands, working with database fixtures or migrations, formatting code, building, testing, or running the server.

It keeps Go code, SQL fixtures, configuration, builds, tests, and runnable commands organized according to the repository's expectations.

How tendant/postgres-mcp-go configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to tendant/postgres-mcp-go. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/tendant/postgres-mcp-go/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/tendant/postgres-mcp-go

Made for: Codex, OpenCode.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/tendant/postgres-mcp-go/agents-md/github.svg)](https://agentmods.dev/instructions/tendant/postgres-mcp-go/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/tendant/postgres-mcp-go/agents-md"><img src="https://agentmods.dev/badge/instructions/tendant/postgres-mcp-go/agents-md/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/tendant/postgres-mcp-go/agents-md"><img src="https://agentmods.dev/badge/instructions/tendant/postgres-mcp-go/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 576 This file is loaded in full into every session.

When invoked 576 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00576	$0.00576
Opus 5.5	$0.00230	$0.00230
Sonnet 5.5	$0.00115	$0.00115
Haiku 4.5	$0.00058	$0.00058

Measured 2mo ago against content hash 3fb85f4bc3a0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

postgres-mcp-go 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 2mo 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.

AGENTS.md · 38 lines

How it starts

The opening of the file, as written. The whole thing — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Repository Guidelines

Project Structure & Module Organization

Module name is github.com/tendant/postgres-mcp-go; keep imports aligned with it.
Place runnable entry points under cmd/ (e.g., cmd/agent/main.go) and reusable packages under internal/ or pkg/.
Store SQL fixtures, migrations, or prompt templates in assets/, and environment samples in configs/.
Use testdata/ for deterministic fixtures; it is automatically ignored by Go tools.
Keep generated binaries, coverage files, and local .env secrets out of version control (already covered in .gitignore).

Build, Test, and Development Commands

make build — compiles and drops bin/postgres-mcp with sandboxed Go caches.
make test — runs go test ./... with the same cached toolchain setup.
make run-stdio — launches the MCP server over stdio (requires DATABASE_URL).
make run-http — launches the HTTP server; add flags via EXTRA_FLAGS (e.g., --http-json).
go mod tidy — normalize module manifests after dependency changes.
go fmt ./... — format code using Go defaults.

Coding Style & Naming Conventions

Follow Go 1.24 defaults: tabs for indentation, one statement per line, no unnecessary semicolons.
Use concise, lowercase package names (postgres, agent) and PascalCase for exported types and functions.
Prefix sentinel errors with Err and wrap upstream errors with %w to preserve context.
Document exported identifiers with complete sentences so godoc output stays clear.

Testing Guidelines

Organize tests as table-driven cases in *_test.go files colocated with the code they cover.
Prefer standard library testing plus testdata/ fixtures; add integration tests under internal/<pkg>/integration_test.go when needed.
Maintain at least 80% package coverage; verify with go test -cover ./... before opening a PR.

Commit & Pull Request Guidelines

Write imperative, 1-line commit subjects similar to the existing history (add go.mod).
Squash unrelated work; each commit should build and pass tests.
PR descriptions must include the problem statement, the solution outline, and local command output (go test ./...).
Link issues with Fixes #123 or Refs #123, and request review only after CI succeeds.

Read the full file on GitHub · 38 lines

Changes

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.

2mo ago First seen · 38 lines · 576 tokens per session scan A 3fb85f4bc3a0

Subscribe to this mod's changes

postgres-mcp-go AGENTS.md is an instructions file published in the GitHub repository tendant/postgres-mcp-go (2 stars, last pushed 1y ago), licensed MIT. It adds 576 tokens to every session, about $0.0023 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.

Building agents Databases PostgreSQL ai-agents mcp-server

postgres-mcp-go AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
postgres-mcp-go AGENTS.mdtendant/postgres-mcp-go	Instructions file	2	1y ago	MIT	A	576	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	9,719	GitHub Copilot
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	5,516	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	today	MIT	A	4,680	Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	3,093	GitHub Copilot
vscode model-prompts.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	2,022	GitHub Copilot

postgres-mcp-go: Instructions file for Codex