What is pg_exporter AGENTS.md?

Repository instructions for pg_exporter, a Rust program that exports PostgreSQL database measurements for monitoring. They describe the project structure, contributor process, development environment, and test commands.

Use them when changing collectors, tests, or other parts of pg_exporter, especially when database-backed checks should run in the documented DevPod environment.

They help coding agents make safe changes while preserving the project's security and testing rules.

pg_exporter AGENTS.md — Instructions file by nbari

Install

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.

agentmods

npx agentmods add instructions/nbari/pg_exporter/agents-md

Clone the repo

git clone --depth 1 https://github.com/nbari/pg_exporter

Made for: Codex, OpenCode.

Per session 2,108 This file is loaded in full into every session.

When invoked 2,108 The same file — it is already loaded in full.

Security scan A 0 findings. Scan, not verified.

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	$0.02108	$0.02108
Opus 5	$0.01054	$0.01054
Sonnet 5	$0.00422	$0.00422
Haiku 4.5	$0.00211	$0.00211

Measured 2d ago against content hash e29063e64639, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

AGENTS.md · 177 lines

How it starts

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

AGENTS.md

These guidelines are mandatory for contributors and for any AI coding agent operating in this repository. The goal is to land changes safely, keep security invariants intact, and keep the workspace consistent over time.

Project Shape

This repository is a single Rust crate, not a Cargo workspace.
Prefer cargo test over cargo test --workspace.
The main entrypoint is pg_exporter, a PostgreSQL metrics exporter written in Rust.

First Steps

Before making non-trivial changes:

Read CONTRIBUTING.md.
Read tests/TESTING.md if touching collectors or tests.
Check .justfile for the supported local workflows.

DevPod Workflow (Preferred)

Prefer the compose-based DevPod environment documented in CONTRIBUTING.md and .devcontainer/README.md for development and database-backed validation.
Start or refresh it with scripts/dev-up, then enter it with scripts/dev-ssh. For non-interactive commands, use devpod ssh pg-exporter --workdir /workspaces/pg_exporter --command '<command>'.
Run setup checks, Rust tests, and collector integration tests inside DevPod so they use the bundled postgres service with pg_stat_statements preloaded.
Do not start a second host-side PostgreSQL container when the DevPod services are available.

Local Commands

Start local PostgreSQL: just postgres
Verify the local test database: ./scripts/setup-local-test-db.sh
Run the standard local validation flow: just test
Formatting is required: cargo fmt --all -- --check
Clippy is required: cargo clippy --all-targets --all-features
Run tests directly when the local DB is already ready:
- PG_EXPORTER_DSN="postgresql://postgres:postgres@localhost:5432/postgres" cargo test

These are not advisory commands. A change is not ready for review if formatting, Clippy, or tests fail locally.

Test Database Rules

Tests must run against local PostgreSQL: localhost:5432 for the host workflow, or the compose postgres:5432 service inside DevPod.
Do not run the test suite against a remote PG_EXPORTER_DSN.
The local PostgreSQL instance must have pg_stat_statements preloaded and the extension created.
Rootless Podman is used in local workflows. Podman networking may invoke pasta; errors from pasta are container-networking failures, not Rust test failures by themselves.

Read the full file on GitHub · 177 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.

2d ago First seen · 177 lines · 2,108 tokens per session scan A e29063e64639

Subscribe to this mod's changes

pg_exporter AGENTS.md is an instructions file published in the GitHub repository nbari/pg_exporter (49 stars, last pushed 11d ago), licensed BSD-3-Clause. It adds 2,108 tokens to every session, about $0.0105 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.

Databases Languages Testing

spec-kit AGENTS.md

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.

github/spec-kit · 7,104 tokens

vscode buildNext.instructions.md

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

microsoft/vscode · 6,785 tokens

pg_exporter AGENTS.md