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-troubleshootingnpx skills add Evokoa/polygres-skills --skill polygres-troubleshootinggit 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.00106 | $0.01006 |
| Opus 5 | $0.00053 | $0.00503 |
| Sonnet 5 | $0.00021 | $0.00201 |
| Haiku 4.5 | $0.00011 | $0.00101 |
Grade A, and why
polygres-troubleshooting 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Polygres Troubleshooting
Use read-only checks first. Resolve context, preserve evidence, classify the failure boundary, and recommend the smallest safe correction. Do not mutate while diagnosing.
Workflow
- Read the installed
polygres --helpand command-specific help before using a command. Installed behavior is the source of truth for CLI compatibility. - Resolve identity, configuration source, and one exact project using
references/context-and-connectivity.md. Stop on an ambiguous project. - Capture the symptom, timestamp, sanitized command or SDK call, exit code or
exception type,
request_id, job ID, and whether pagination returned a cursor. For generated pipelines, also capture the manifest state, plan digest, approved action IDs, checkpoint, and last successfully completed stage. - Inspect project and database evidence with
references/projects-and-database.md. - If
project_modeissynced, usereferences/synced-projects.mdand skip target database, row, import, and migration checks. - For import job or migration failures, use
references/jobs-and-migrations.md. For graph, vector, text, hybrid, or general readiness failures, usereferences/retrieval.md. For pgContext capability, collection, point, operation, recall, or Joint failures, usereferences/context.md. - Classify the fault as CLI/local configuration, control-plane, Runtime API,
Postgres/database or pooler, or asynchronous job state. Use
references/errors-and-escalation.mdfor typed SDK errors and escalation. - Re-check status before retry. Recommend a corrective action, but obtain
explicit approval and delegate supported mutations to
$polygres-clior application changes to$polygres-sdk.
For a single-row write that lost the response after submission, treat the
commit outcome as ambiguous unless public evidence resolves it. Do not
automatically retry a row-only insert, upsert, or ignore. For a Context-backed
write, replay the exact request with its exact idempotency key within the
24-hour replay window; the composite ledger prevents another row mutation.
After ROW_CONTEXT_IDEMPOTENCY_EXPIRED, inspect the row and Context point before
choosing a new key.
What ships with it
8 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.
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 · 84 lines · 106 tokens per session scan A 4e204a86f49a
polygres-troubleshooting is a skill published in the GitHub repository Evokoa/polygres-skills (10 stars, last pushed 14d ago), licensed Apache-2.0. It adds 106 tokens to every session and 1,006 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
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 …
postgres-pro
Use when optimizing PostgreSQL queries, configuring replication, or implementing advanced database features. Invoke for EXPLAIN analysis, JSONB operations, extension usage, VACUUM tuning, performance monitoring.
postgres-database-migration
Use this skill for planning, testing, and safely executing PostgreSQL schema migrations — especially when working with production data or shared databases. Trigger when user asks to: Test a schema migration before applying it to production Add, remove, or rename columns safely on a live table Change a column's data…
setup-timescaledb-hypertables
Use this skill when creating database schemas or tables for Timescale, TimescaleDB, TigerData, or Tiger Cloud, especially for time-series, IoT, metrics, events, or log data. Use this to improve the performance of any insert-heavy table. Trigger when user asks to: Create or design SQL schemas/tables AND…
claimable-postgres
Provision instant temporary Postgres databases via Claimable Postgres by Neon (neon.new) with no login, signup, or credit card. Supports REST API, CLI, and SDK. Use when users ask for a quick Postgres environment, a throwaway DATABASEURL for prototyping/tests, or "just give me a DB now". Triggers include: "quick…
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, FK…