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 skills/eslider/2dph/postgresnpx skills add eSlider/2dph --skill postgresgit clone --depth 1 https://github.com/eSlider/2dphWhat 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.00041 | $0.00375 |
| Opus 5 | $0.00020 | $0.00187 |
| Sonnet 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 yesterday.
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.
- yesterday First seen · 40 lines · 41 tokens per session scan A 05da5fdc35cf
postgres is a skill published in the GitHub repository eSlider/2dph (2 stars, last pushed 2d ago), licensed MIT. It adds 41 tokens to every session and 375 once invoked, about $0.0002 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-31.
Other skills, from other repositories
engrama-onboard
Build a personalized Engrama memory graph for any user through a conversational interview. Use this skill whenever someone says "set up Engrama", "create my graph", "onboard", "build my profile", "configure Engrama for me", or asks how to start using Engrama. Also use when the user mentions they have a different role…
life-memory-mcp-connect
Set up an external AI agent to connect to the Life Memory System through MCP, including verified installation, retrieval, RawEvent writes, sync, diagnostics, and Working-Agent governance. Use when an agent needs to install or verify the Life Memory MCP bridge, onboard Codex/Claude/Cursor/Windsurf style clients, or…
life-memory-media-ingestion
Teach an external agent how to send links, files, images, tables, audio, and video into the Life Memory System as reviewable media note artifacts through MCP.
fortemi-roadmap-skill
Advance the Fortemi delivery roadmap by one concrete increment and document the progress. Reads .aiwg/planning/roadmap.md, picks the next actionable item respecting phase gating, does or dispatches the work, then records progress back into the roadmap. Built for fresh sessions and simple loops.
fortemi-monthly-report
Author a Fortémi monthly report as a docsite blog post — gather what shipped that month from git history, CHANGELOG, and release announcements, then write it up FOR USERS in plain language and publish it to the Pagenary blog collection.
graph-mutation-plan
Cookbook for composing an applygraphmutations plan — stable entitykey patterns, the canonical label/edge vocabulary, evidence/invalidation/confidence discipline, and a worked example. Load this when building a non-trivial mutation plan.