polygres-cli

polygres-cli is a skill for Claude Code, Codex from Evokoa/polygres-skills. It costs 67 tokens per session (2,102 once invoked), scanned A, original, Apache-2.0.

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

In plain words
What is it for?
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.
Why use it?
It defines safe steps for authentication, project selection, version checks, data changes, imports, migrations, retrieval setup, and key management.

Skill for Claude CodeCodex

Written for Claude Code and Codex: shipped in a Claude Code plugin, but also agents/openai.yaml present.

Part of the polygres plugin — 5 skills, 1 MCP server shipped together

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

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/evokoa/polygres-skills/polygres-cli
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-cli
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.

agentmods badge for polygres-cli

README.md
[![agentmods](https://agentmods.dev/badge/skills/evokoa/polygres-skills/polygres-cli/github.svg)](https://agentmods.dev/skills/evokoa/polygres-skills/polygres-cli)
Your own site
<a href="https://agentmods.dev/skills/evokoa/polygres-skills/polygres-cli"><img src="https://agentmods.dev/badge/skills/evokoa/polygres-skills/polygres-cli/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.

agentmods 80×15 button for polygres-cli

Your own site · 80×15
<a href="https://agentmods.dev/skills/evokoa/polygres-skills/polygres-cli"><img src="https://agentmods.dev/badge/skills/evokoa/polygres-skills/polygres-cli.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 67 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,102 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00067 $0.02102
Opus 5.5 $0.00027 $0.00841
Sonnet 5.5 $0.00013 $0.00420
Haiku 4.5 $0.00007 $0.00210

Measured 1mo ago against content hash ddb824dea206, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 1mo ago.

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 · 178 lines

How it starts

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

Prefer an available MCP connection

When Polygres MCP tools are available in the current session, read references/mcp-tool-contract.md and use the discovered compatible tools for interactive project operations. Call whoami, respect the fixed-project or multi-project boundary, and treat the discovered catalog as authoritative.

Use the CLI workflow in this skill when the user explicitly asks for CLI, when MCP is absent or incompatible, or when the operation belongs to the CLI surface, such as migrations, Runtime keys, interactive database access, import start, and legacy vector or text configuration. Never invent an MCP tool to mirror a CLI command.

Start safely

  1. Run polygres --version and polygres --help before live or end-to-end testing, and whenever availability or command compatibility is unknown.
  2. 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.
  3. 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.
  4. 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.
  5. Run polygres whoami before a mutation when identity or active organization is uncertain. Use polygres login when authentication is required.
  6. 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.
  7. Resolve project_mode. When it is synced, read references/synced-projects.md before choosing any command.
  8. Prefer polygres --json ... for output the agent must parse. Treat stdout as the JSON channel and stderr as diagnostics.

Read the full file on GitHub · 178 lines

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.

  1. 1mo ago Changed ddb824dea206
  2. 1mo ago Changed · +9 lines 6eecce5dc692
  3. 1mo ago Changed · +14 lines · -30 tokens per session 7e3c627d2c54
  4. 1mo ago 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 1mo ago), licensed Apache-2.0. It adds 67 tokens to every session and 2,102 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

alloydb-basics

Manages clusters, instances, and backups for AlloyDB for PostgreSQL, and integrates with AlloyDB Model Context Protocol (MCP) tools for automated database operations. Use when creating, configuring, or administering AlloyDB databases. Do NOT use for general PostgreSQL instances (e.g. Cloud SQL) or other GCP databases.

google/skills · 72 tokens

postgresql-table-design

Use this skill when designing or reviewing a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features.

wshobson/agents · 37 tokens

db-repair

Auto-fix gbrain's Postgres access so the brain stays available. When any gbrain command or MCP tool result carries a GBRAINDBACCESS marker (or an operator reports the brain database is down), run the hardcoded gbrain db-repair ladder: diagnose, apply the safe tier, verify. The action is ALWAYS the hardcoded command …

garrytan/gbrain · 96 tokens

volcengine-rds-postgresql

A tool for operating PostgreSQL databases hosted by Volcano Engine's managed database service. PostgreSQL is a relational database used to store structured application data.

bytedance/agentkit-samples · 63 tokens

dsql

Build with Aurora DSQL — manage schemas, execute queries, handle migrations, diagnose query plans, diagnose cluster performance, load data, and develop applications with a serverless, distributed SQL database. Covers IAM auth, multi-tenant patterns, MySQL-to-DSQL and PostgreSQL-to-DSQL schema conversion, foreign key…

awslabs/agent-plugins · 246 tokens

polar-local-environment

This skill should be used when setting up or managing Polar local development environment with Docker.

fcakyon/claude-codex-settings · 22 tokens