What is polygres-cli?

Instructions for operating Polygres projects through its command-line tool. Polygres is a service for storing application data and configuring searches over it.

It helps create and inspect projects, write records, import data, apply database migrations, configure graph or text retrieval, manage Runtime keys, and run durable operations.

It defines safe steps for authentication, project selection, version checks, data changes, imports, migrations, retrieval setup, and key management.

polygres-cli — Skill 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.

agentmods

npx agentmods add skills/evokoa/polygres-skills/polygres-cli

Any agent

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

Clone the repo

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

Made for: Claude Code, Codex.

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

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

Security scan A 0 findings. Scan, not verified.

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	$0.00097	$0.01747
Opus 5	$0.00048	$0.00873
Sonnet 5	$0.00019	$0.00349
Haiku 4.5	$0.00010	$0.00175

Measured yesterday against content hash 828ef5aabcfc, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/prepare_import.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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-cli/SKILL.md · 155 lines

How it starts

The opening of the file, as written. The whole thing — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Polygres CLI

Operate a user's Polygres project through the installed polygres command. Treat the CLI as the operational and security boundary. Do not call private control-plane routes or infer undocumented request payloads.

Start safely

Run polygres --version and polygres --help before live or end-to-end testing, and whenever availability or command compatibility is unknown.
If the command is missing, tell the user how to install polygres-cli and let them approve or perform the installation. Do not install packages silently.
For live tests from a Polygres source checkout, create an isolated test environment, reinstall both polygres-cli and polygres-sdk from that checkout under its dependency-installation policy, and verify their versions and import origins before testing. Do not substitute PyPI packages for the checkout under test.
Outside a source checkout, compare installed CLI and SDK versions with the versions required by the application or current skill compatibility record. Do not call an installation current merely because the command exists. Obtain approval before changing installed packages.
Run polygres whoami before a mutation when identity or active organization is uncertain. Use polygres login when authentication is required.
Resolve the project with polygres projects list, an explicit --project, or polygres projects use <project>. State the resolved project before a destructive, secret-producing, or schema-mutating operation.
Resolve project_mode. When it is synced, read references/synced-projects.md before choosing any command.
Prefer polygres --json ... for output the agent must parse. Treat stdout as the JSON channel and stderr as diagnostics.

If bundled examples differ from the installed --help, follow the installed command surface and explain the version mismatch. Never guess a replacement.

Route the request

Read only the references needed for the task:

Read the full file on GitHub · 155 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.

yesterday First seen · 155 lines · 97 tokens per session scan A 828ef5aabcfc

Subscribe to this mod's changes

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

Databases Research

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

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…

openai/codex · 114 tokens

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…

openai/codex · 113 tokens

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…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens