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/evokoa/polygres-skills/polygres-sdknpx skills add Evokoa/polygres-skills --skill polygres-sdkgit clone --depth 1 https://github.com/Evokoa/polygres-skillsWhat 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.00102 | $0.01254 |
| Opus 5 | $0.00051 | $0.00627 |
| Sonnet 5 | $0.00020 | $0.00251 |
| Haiku 4.5 | $0.00010 | $0.00125 |
Grade A, and why
polygres-sdk 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.
How it starts
The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Polygres SDK
Build Python application code against the public polygres-sdk package and a
project's Runtime API. Use $polygres-cli instead for human authentication,
control-plane project administration, imports, migrations, and API-key management.
Workflow
- Inspect
pyproject.toml, requirements files, and existing client setup. - Confirm the installed
polygres-sdkandpolygres-cliversions before live or end-to-end testing. If testing a Polygres source checkout, create an isolated environment, reinstall both packages from that checkout under its dependency-installation policy, and verify their versions and import origins. Do not substitute PyPI packages for the checkout under test. - Outside a source checkout, compare both installed versions with the application requirements or current skill compatibility record. Obtain approval before installing or changing dependencies.
- Resolve
POLYGRES_API_KEYandPOLYGRES_RUNTIME_URLfrom server-side environment configuration. Never log or embed either value. - Confirm that the URL is the per-project Runtime API URL, not the Polygres control-plane URL or a direct or pooled Postgres URL.
- Resolve project mode before selecting a namespace. For a synced project,
construct
client.project(project_mode="synced")and readreferences/synced-projects.md. - Check
project.readiness()before relying on graph, existing vector, or legacy hybrid retrieval. For new semantic retrieval, prefer Polygres AI Context: callproject.context.get_capabilities()and then inspect collection status or verification. Useproject.connection_info()only for passwordless connection metadata. - Keep every pgContext call on the flat
project.contextnamespace. Prefer$polygres-clifor interactive setup. Use SDK mutations for explicit, backend-owned automation, return them immediately, and wait only when the application workflow requires a terminal result. - Choose one focused retrieval call. Use real row IDs returned by the SDK or verified application data; never invent graph identifiers.
- Bound depth, candidate counts, result limits, pagination, and application token budget. Apply authorization before retrieval because filters are not an authorization boundary.
- Preserve result provenance, request IDs, and typed models through RAG assembly. Deduplicate before constructing context.
- Handle the documented exception hierarchy and test success, malformed responses, fuzzy or empty queries, invalid dimensions, and transient errors.
What ships with it
9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- agents/openai.yaml 212 B
- references/client-setup.md 4.0 KB
- references/context.md 14 KB
- references/errors-pagination-testing.md 3.5 KB
- references/graph-retrieval.md 2.6 KB
- references/hybrid-and-rag.md 2.3 KB
- references/rows.md 3.8 KB
- references/synced-projects.md 2.4 KB
- references/vector-and-text.md 3.1 KB
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 · 99 lines · 102 tokens per session scan A 0d79fa999177
polygres-sdk is a skill published in the GitHub repository Evokoa/polygres-skills (10 stars, last pushed 13d ago), licensed Apache-2.0. It adds 102 tokens to every session and 1,254 once invoked, about $0.0005 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…