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/baseballyama/eslint-plugin-postgresql/claude-mdgit clone --depth 1 https://github.com/baseballyama/eslint-plugin-postgresqlWhat 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.03361 | $0.03361 |
| Opus 5 | $0.01681 | $0.01681 |
| Sonnet 5 | $0.00672 | $0.00672 |
| Haiku 4.5 | $0.00336 | $0.00336 |
Grade A, and why
eslint-plugin-postgresql CLAUDE.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 3d 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 — 302 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
eslint-plugin-postgresql is an ESLint plugin that lints PostgreSQL SQL files.
It ships rules that detect syntax errors and enforce PostgreSQL-specific best
practices, using postgresql-eslint-parser
(which itself wraps libpg-query)
to parse .sql files into an ESLint-compatible AST.
Project overview
- Audience: OSS — code that external contributors and end users will read.
- Language / stack: TypeScript, ESM-only, published to npm as
eslint-plugin-postgresql. Built with rolldown, tested with vitest, type- checked withtsc, linted with oxlint, formatted with Prettier. - Package manager: pnpm. Lockfile is committed. Use
pnpm install --frozen-lockfilein CI. - Public API: the default export from
dist/index.js— apluginobject exposingrulesandconfigs.recommended. Anything not reachable through that export is internal. - Related projects:
postgresql-eslint-parser— parser layer.libpg-query— actual PostgreSQL parser. Bugs in those layers should go upstream, not here.
OSS is not the same as "code only I touch." Optimize for a stranger not getting confused, not for your own convenience.
Repository layout
| Path | Purpose |
|---|---|
src/index.ts |
Plugin entry point (rules, configs.recommended). |
src/rules/*.ts |
One file per rule. Export an ESLint rule object as default. |
src/meta.ts |
Package name / version pulled into the plugin meta. |
tests/*.test.ts |
Vitest unit tests, one per rule plus an index smoke test. |
tests/fixtures/<rule>/ |
SQL fixtures + sibling <basename>.yaml snapshots. |
tests/test-utils.ts |
Shared test helpers (linter wiring, YAML fixture loader). |
scripts/create-rule.js |
Scaffold a new rule + tests + fixture directory. |
dist/ |
Build output (gitignored except for publish). |
.changeset/ |
Pending changesets — drive the release PR. |
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.
- 3d ago First seen · 302 lines · 3,361 tokens per session scan A 6d1d8e272bad
eslint-plugin-postgresql CLAUDE.md is an instructions file published in the GitHub repository baseballyama/eslint-plugin-postgresql (11 stars, last pushed 3d ago), licensed MIT. It adds 3,361 tokens to every session, about $0.0168 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
expense-budget-tracker AGENTS.md
Instructions for kirill-markin/expense-budget-tracker, covering expense-budget-tracker, rules, components, supported clients and key paths.
postgres-skills AGENTS.md
Instructions for neondatabase/postgres-skills, covering agents.md, repository overview, creating a new skill, directory structure and naming conventions.
pg_exporter AGENTS.md
Instructions for nbari/pg_exporter, covering agents.md, project shape, first steps, devpod workflow (preferred) and local commands.
ai-dba-workbench CLAUDE.md
Claude Code instructions for pgEdge/ai-dba-workbench, covering claude standing instructions, primary agent role, trivial-edit carve-out, project structure and key files.
mcp-database CLAUDE.md
Claude Code instructions for DiegoBulhoes/mcp-database, covering claude.md, commands, architecture, invariants (do not weaken) and adding or changing a tool.
pgbent copilot-instructions.md
Copilot instructions for gregs1104/pgbent: This file exists for GitHub Copilot compatibility. The canonical agent guide is AGENTS.md at the repository root.