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 skills add eSlider/2dph --skill postgresgit clone --depth 1 https://github.com/eSlider/2dphWrote 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.
[](https://agentmods.dev/skills/eslider/2dph/postgres)<a href="https://agentmods.dev/skills/eslider/2dph/postgres"><img src="https://agentmods.dev/badge/skills/eslider/2dph/postgres/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.
<a href="https://agentmods.dev/skills/eslider/2dph/postgres"><img src="https://agentmods.dev/badge/skills/eslider/2dph/postgres.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00041 | $0.00375 |
| Opus 5.5 | $0.00016 | $0.00150 |
| Sonnet 5.5 | $0.00008 | $0.00075 |
| Haiku 4.5 | $0.00004 | $0.00038 |
Grade A, and why
postgres 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 1mo 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
postgres
bin/postgres/query.go wraps vendored scripts/db/psql-yq. Output is YAML
(cheaper than psql ASCII, easy to slice with mikefarah/yq).
bin/postgres/query.go --profile onlyoffice -s document_asset # column list
bin/postgres/query.go --profile onlyoffice -t task_result -l 20 # sample rows
bin/postgres/query.go --profile onlyoffice -c 'SELECT ...' # query → YAML
Ad-hoc targets without a profile:
bin/postgres/query.go --container my-pg --db app -c 'SELECT 1'
bin/postgres/query.go --dsn 'postgres://user@host:5432/db' -c 'SELECT 1'
Profiles
Connection details live in $HOME/.config/brain/db-profiles.yml (mode 600),
never in a project repo. A profile names either a container or a host;
passwords are read from a separate password_env_file and never appear in argv.
Rules
- Read-only. Any
insert|update|delete|drop|truncate|alter|create|grant| revoke|vacuum|copyis rejected with exit 3. Do not work around it. - PII. Client CRM databases: aggregate and count freely; never copy names or addresses into chat, issues or docs.
- Use
-lto keep samples small. Twenty rows answer most questions.
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.
- 1mo ago First seen · 40 lines · 41 tokens per session scan A 05da5fdc35cf
postgres is a skill published in the GitHub repository eSlider/2dph (3 stars, last pushed 24d ago), licensed MIT. It adds 41 tokens to every session and 375 once invoked, about $0.0002 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.
Other skills, from other repositories
db-design
Design and evolve PostgreSQL schemas that survive scale and refactors. Use when modeling a new domain, choosing between normalization and denormalization, designing indexes for known query patterns, writing migrations safely, picking ORM-vs-raw-SQL trade-offs, deciding on soft delete vs hard delete, or evaluating…
supabase
Build on Supabase correctly — Row Level Security, auth, realtime, storage, edge functions, and the Postgres underneath. Use when wiring a Supabase client, writing or reviewing RLS policies, debugging "anyone can read everyone's rows", setting up auth, adding realtime subscriptions, handling file storage, or deciding…
connectors
PostgreSQL connector and inspect() live in this package; graph product routing: SKILL.md.
claude-memory
Access the persistent memory database (PostgreSQL claudememory) for long-term context across Claude Code sessions. Triggers on "what do I know about", "memory lookup", "recall", "memory db", "what did we decide about", "similar conversations", "lookup context", "/memory". Provides semantic search, SQL queries and the…
setup-people-memory
Set up or reconfigure People Memory for an existing Codex, Claude Code, Cursor, or other MCP-capable agent; create a minimal personal agent if needed; choose local PostgreSQL or hosted Supabase; install the schema, MCP, UI, and durable memory instructions; ask which LinkedIn, Google Contacts, WhatsApp, Gmail…
upgrade-people-memory
Upgrade an installed People Memory plugin, MCP package, PostgreSQL/Supabase schema, optional API, web UI, and bundled skills; inspect release notes, back up data, apply ordered migrations, refresh uvx or local installs, preserve config and credentials, restart agents, and verify reads and writes. Use when the user…