polygres-data-pipeline

polygres-data-pipeline is a skill for Claude Code, Codex from Evokoa/polygres-skills. It costs 63 tokens per session (3,005 once invoked), scanned A, original, Apache-2.0.

A decision guide for setting up or extending Polygres, a data pipeline that can support ingestion, memory, graphs, embeddings, synchronization, and retrieval.

In plain words
What is it for?
Use it to plan or implement data ingestion, search and retrieval, embeddings, graph relationships, backfills, or continuous data capture.
Why use it?
It helps choose only the pipeline parts needed for the intended result while preserving authorization, source tracking, secrets, and compatibility.

Skill for Claude CodeCodex

Written for Claude Code and Codex: shipped in a Claude Code plugin, but also agents/openai.yaml present. Also seen: mentions Claude Code; mentions AGENTS.md; mentions Codex.

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

Good fit Use it to plan or implement data ingestion, search and retrieval, embeddings, graph relationships, backfills, or continuous data capture.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/evokoa/polygres-skills/polygres-data-pipeline"><img src="https://agentmods.dev/badge/skills/evokoa/polygres-skills/polygres-data-pipeline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,005 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00063 $0.03005
Opus 5.5 $0.00025 $0.01202
Sonnet 5.5 $0.00013 $0.00601
Haiku 4.5 $0.00006 $0.00300

Measured 1mo ago against content hash f65c767b2f71, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

polygres-data-pipeline 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 9 executable files (assets/python-pipeline/checkpoint_ledger.py, assets/python-pipeline/local_embeddings.py, scripts/check_embedding_device.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-data-pipeline/SKILL.md · 265 lines

How it starts

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

Polygres Data Pipeline

Turn setup intent into the smallest complete working result. Adapt to what the user actually needs. Do not force every setup through schema creation, embeddings, graph, backfill, continuous capture, retrieval code, or agent instructions.

Use guidance at the right strength

Treat this skill as a decision guide, not a mandatory architecture or ordered checklist. Adapt, reorder, replace, or omit recommended components and numeric defaults when inspected evidence or the user's outcome supports a better design. Numeric defaults are starting points, including sample sizes, result counts, token budgets, recall timing, capture timing, and model rankings.

Keep only safety and correctness boundaries firm: preserve authorization and provenance, keep secrets out of plans and payloads, disclose and approve material effects, use compatible embedding contracts, avoid unsupported public interfaces and invented graph relationships, and test the important selected path before calling it operational.

Choose the execution surface

When Polygres MCP tools are available, read references/mcp-tool-contract.md, call whoami, and prefer discovered compatible MCP tools for interactive inspection, setup, retrieval, and operation tracking. Treat the connection's project boundary, feature selection, read-only setting, and visible catalog as authoritative.

Use the existing CLI, SDK, Dashboard, or PostgreSQL workflow when MCP is absent, incompatible, or does not expose the required operation. Keep the SDK for persistent application code, the Dashboard for source secret entry and import start, and the CLI for migrations, Runtime keys, and other documented operator workflows.

Recognize setup intent

Activate for broad prompts such as "Help me set up Polygres," contextual prompts such as "look at my conversations and set up Polygres," and detailed technical specifications. Treat examples as illustrations, not required wording.

Read the full file on GitHub · 265 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 f65c767b2f71
  2. 1mo ago Changed · +3 lines ed9502147d40
  3. 1mo ago Changed · +23 lines · -120 tokens per session d0a73d13a615
  4. 1mo ago First seen · 239 lines · 183 tokens per session scan A 32d69444d57a

Subscribe to this mod's changes

polygres-data-pipeline is a skill published in the GitHub repository Evokoa/polygres-skills (10 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 63 tokens to every session and 3,005 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.