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 skills add Evokoa/polygres-skills --skill polygres-cligit clone --depth 1 https://github.com/Evokoa/polygres-skillsWrote 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.
[](https://agentmods.dev/skills/evokoa/polygres-skills/polygres-cli)<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.
<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>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.00067 | $0.02102 |
| Opus 5.5 | $0.00027 | $0.00841 |
| Sonnet 5.5 | $0.00013 | $0.00420 |
| Haiku 4.5 | $0.00007 | $0.00210 |
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.
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 — 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
- Run
polygres --versionandpolygres --helpbefore 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-cliand 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-cliandpolygres-sdkfrom 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 whoamibefore a mutation when identity or active organization is uncertain. Usepolygres loginwhen authentication is required. - Resolve the project with
polygres projects list, an explicit--project, orpolygres projects use <project>. State the resolved project before a destructive, secret-producing, or schema-mutating operation. - Resolve
project_mode. When it issynced, readreferences/synced-projects.mdbefore choosing any command. - Prefer
polygres --json ...for output the agent must parse. Treat stdout as the JSON channel and stderr as diagnostics.
What ships with it
14 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 244 B
- references/authentication-and-projects.md 2.5 KB
- references/automation-and-errors.md 2.6 KB
- references/context.md 14 KB
- references/data-imports.md 5.5 KB
- references/database-and-keys.md 2.1 KB
- references/embeddings.md 14 KB
- references/mcp-graph-retrieval.md 1.1 KB
- references/mcp-tool-contract.md 14 KB
- references/migrations.md 1.2 KB
- references/retrieval.md 5.9 KB
- references/rows.md 4.5 KB
- references/synced-projects.md 6.5 KB
- scripts/prepare_import.py 24 KB runs code
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 ddb824dea206
- 1mo ago Changed · +9 lines 6eecce5dc692
- 1mo ago Changed · +14 lines · -30 tokens per session 7e3c627d2c54
- 1mo ago First seen · 155 lines · 97 tokens per session scan A 828ef5aabcfc
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.
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.
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.
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 …
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.
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…
polar-local-environment
This skill should be used when setting up or managing Polar local development environment with Docker.