What is polygres-sdk?

Instructions for using the Polygres Python SDK, a programming package for writing application records and searching project data through Polygres' Runtime API.

It supports writing records, graph, text, hybrid, vector, and Polygres AI Context queries, plus managing supported collections, points, and durable operations.

It helps developers use the correct project connection and supported retrieval methods without exposing API keys or confusing the Runtime API with other database endpoints.

polygres-sdk — Skill for Claude Code and Codex by Evokoa

Install

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.

Any agent

npx skills add Evokoa/polygres-skills --skill polygres-sdk

Clone the repo

git clone --depth 1 https://github.com/Evokoa/polygres-skills

Made for: Claude Code, Codex.

Or install polygres, the plugin that ships this one along with the rest of its 5 skills, 1 MCP server.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/evokoa/polygres-skills/polygres-sdk/github.svg)](https://agentmods.dev/skills/evokoa/polygres-skills/polygres-sdk)

Your own site

<a href="https://agentmods.dev/skills/evokoa/polygres-skills/polygres-sdk"><img src="https://agentmods.dev/badge/skills/evokoa/polygres-skills/polygres-sdk/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/evokoa/polygres-skills/polygres-sdk"><img src="https://agentmods.dev/badge/skills/evokoa/polygres-skills/polygres-sdk.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,508 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00049	$0.01508
Opus 5.5	$0.00020	$0.00603
Sonnet 5.5	$0.00010	$0.00302
Haiku 4.5	$0.00005	$0.00151

Measured 1mo ago against content hash 25873fb3f178, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

plugins/polygres/skills/polygres-sdk/SKILL.md · 115 lines

How it starts

The opening of the file, as written. The whole thing — 115 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.

For an interactive grounded answer, prefer available Polygres MCP tools. Read references/mcp-tool-contract.md and references/mcp-grounded-context.md, then use the discovered read catalog. Continue with the SDK workflow for persistent Python application integration, backend-owned automation, or an MCP fallback.

Workflow

Inspect pyproject.toml, requirements files, and existing client setup.
Confirm the installed polygres-sdk and polygres-cli versions 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_KEY and POLYGRES_RUNTIME_URL from 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 read references/synced-projects.md.
Check project.readiness() before relying on graph, existing vector, or legacy hybrid retrieval. For new semantic retrieval, prefer Polygres AI Context: call project.context.get_capabilities() and then inspect collection status or verification. Use project.connection_info() only for passwordless connection metadata.
Keep every pgContext call on the flat project.context namespace. Prefer $polygres-cli for 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. With SDK 0.5.0, pass text when the selected vector is linked to a saved embedding configuration and the Runtime supports query_embedding_generation. Otherwise use an application-supplied vector with the matching model and dimensions. Use real row IDs returned by the SDK or verified application data for graph anchors.
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.

Read the full file on GitHub · 115 lines

Files

What ships with it

11 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.

Changes

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 Changed 25873fb3f178
1mo ago Changed · +8 lines · -3 tokens per session a9933955c5e7
1mo ago Changed · +8 lines · -50 tokens per session c2f0c76acee4
1mo ago First seen · 99 lines · 102 tokens per session scan A 0d79fa999177

Subscribe to this mod's changes

polygres-sdk is a skill published in the GitHub repository Evokoa/polygres-skills (10 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 49 tokens to every session and 1,508 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.

Data and AI RAG and vectors

agent-platform-rag-engine-management

Manage and query Agent Platform RAG Engine Corpora and retrieve grounded contexts using the Google GenAI SDK. Use when listing RAG corpora or files, inspecting a corpus, retrieving contexts, or generating content grounded in a RAG corpus. Do not use for standard database queries (use SQL/Spanner skills), Google…

google/skills · 85 tokens

llm-app-patterns

Production-ready patterns for building LLM applications. Covers RAG pipelines, agent architectures, prompt IDEs, and LLMOps monitoring. Use when designing AI applications, implementing RAG, building agents, or setting up LLM observability.

davila7/claude-code-templates · 54 tokens

9router-embeddings

Generate vector embeddings via 9Router /v1/embeddings using OpenAI / Gemini / Mistral / Voyage / Nvidia / GitHub embedding models for RAG, semantic search, similarity. Use when the user wants embeddings, vectors, RAG, semantic search, or to embed text.

decolua/9router · 66 tokens

similarity-search-patterns

Implement efficient similarity search with vector databases. Use when building semantic search, implementing nearest neighbor queries, or optimizing retrieval performance.

foryourhealth111-pixel/Vibe-Skills · 30 tokens

embedding-strategies

Select and optimize embedding models for semantic search and RAG applications. Use when choosing embedding models, implementing chunking strategies, or optimizing embedding quality for specific domains.

foryourhealth111-pixel/Vibe-Skills · 37 tokens

browserwing-admin

Manage and operate BrowserWing — an intelligent browser automation platform. Install dependencies, configure LLM, create/manage/execute automation scripts, use AI-driven exploration to generate scripts, browse the script marketplace, and troubleshoot issues.

MemTensor/MemOS · 47 tokens