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 commands/postgres-ai/postgresai/pgai-checkupgit clone --depth 1 https://github.com/postgres-ai/postgresaiWhat 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.00000 | $0.00144 |
| Opus 5 | $0.00000 | $0.00072 |
| Sonnet 5 | $0.00000 | $0.00029 |
| Haiku 4.5 | $0.00000 | $0.00014 |
Grade A, and why
pgai:checkup 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.
What it actually says
Health check
Run health checks on a Postgres database.
$ARGUMENTS should be a connection string like postgresql://user@host:5432/db
If password is needed, use one of these methods (in order of preference):
.pgpassfile (~/.pgpass) - most secure, not visible in process listingsPGPASSFILEenvironment variable pointing to a password filePGPASSWORDenvironment variable (visible in process listings on some systems)
postgresai checkup $ARGUMENTS
Present the report output to the user. Add a brief summary at the end highlighting the most critical issues and recommended next steps.
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 · 17 lines · 0 tokens per session scan A ffd1e627e0ad
pgai:checkup is a command published in the GitHub repository postgres-ai/postgresai (132 stars, last pushed 5d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 144 tokens. 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 commands, from other repositories
psql-query
Run ad-hoc PostgreSQL analytics queries against dev/test database.
cms
Set up Payload CMS in this app, backed by Supabase.
db
Set up or operate Supabase Postgres for this project.
postgresql-database
Directly invoke the postgresql-database skill, bypassing natural-language trigger matching.
setup-database
This command provides database setup instructions. When this command is used in a task, it will automatically include rules that are tagged with database: postgres and feature: auth in their frontmatter.
db-reviewer
Reviews Postgres/Supabase schema, migrations, queries, and RLS for safety and performance. Use when DB code changes, before applying a migration, or inside /...