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-troubleshootinggit 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-troubleshooting)<a href="https://agentmods.dev/skills/evokoa/polygres-skills/polygres-troubleshooting"><img src="https://agentmods.dev/badge/skills/evokoa/polygres-skills/polygres-troubleshooting/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-troubleshooting"><img src="https://agentmods.dev/badge/skills/evokoa/polygres-skills/polygres-troubleshooting.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.00069 | $0.01209 |
| Opus 5.5 | $0.00028 | $0.00484 |
| Sonnet 5.5 | $0.00014 | $0.00242 |
| Haiku 4.5 | $0.00007 | $0.00121 |
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 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 — 97 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.
When Polygres MCP tools are available, read
references/mcp-tool-contract.md, call whoami, and use the discovered read
catalog before CLI or SDK fallback. Treat the connection URL restrictions,
OAuth installation, current scopes, project boundary, project mode, and catalog
version as separate diagnostic layers.
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. For embedding setup, generation, text query models, or usage, usereferences/embeddings.md. Usereferences/mcp-retrieval-quality.mdfor retrieval evaluation through MCP andreferences/mcp-operation-recovery.mdfor MCP operation state. - 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 the smallest corrective action and
hand off supported mutations to
$polygres-clior application changes to$polygres-sdk, using the user's existing authorization when it covers the action.
What ships with it
12 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 237 B
- references/context-and-connectivity.md 1.3 KB
- references/context.md 5.8 KB
- references/embeddings.md 13 KB
- references/errors-and-escalation.md 2.5 KB
- references/jobs-and-migrations.md 1.0 KB
- references/mcp-operation-recovery.md 2.0 KB
- references/mcp-retrieval-quality.md 2.1 KB
- references/mcp-tool-contract.md 14 KB
- references/projects-and-database.md 1.3 KB
- references/retrieval.md 3.4 KB
- references/synced-projects.md 3.9 KB
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 7dcfbe061f62
- 1mo ago Changed · +5 lines · -1 tokens per session df7445e76b42
- 1mo ago Changed · +8 lines · -36 tokens per session 0118b41b66c8
- 1mo 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 1mo ago), licensed Apache-2.0. It adds 69 tokens to every session and 1,209 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
sql-optimizer
Analyzes SQL queries for missing indexes, N+1 patterns, suboptimal joins, and full table scans. Interprets EXPLAIN, detects anti-patterns, rewrites queries. Triggers on: "optimize this query", "slow query", "add indexes", "explain plan", "N+1 query", "why is this query slow".
ecto-constraint-debug
Debug Ecto constraint violations - trace triggers, check migrations, find duplicate data. Use when seeing uniqueconstraint, foreignkeyconstraint, or checkconstraint errors.
sql-optimization-patterns
Master SQL query optimization, indexing strategies, and EXPLAIN analysis to dramatically improve database performance and eliminate slow queries. Use when debugging slow queries, designing database schemas, or optimizing application performance.
rls-performance
A guide for finding and fixing slow database queries when row-level security rules and limited connection pools affect an API.
sql-explain
Explains a PostgreSQL EXPLAIN ANALYZE plan and points at the slowest node. Use when the user pastes a query plan; not for rewriting schemas.
optimize-a-query
Diagnose and fix a slow Postgres query in the builders-stack — read its EXPLAIN plan, find the missing index or the ORM N+1, and confirm the fix. Use when a page or endpoint is slow, a query times out, or pgstatstatements shows a hot query. Pairs with design-a-schema for the index itself.