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.
git clone --depth 1 https://github.com/estuary/agent-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/plugins/estuary/agent-skills/estuary-materializations)<a href="https://agentmods.dev/plugins/estuary/agent-skills/estuary-materializations"><img src="https://agentmods.dev/badge/plugins/estuary/agent-skills/estuary-materializations/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/plugins/estuary/agent-skills/estuary-materializations"><img src="https://agentmods.dev/badge/plugins/estuary/agent-skills/estuary-materializations.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
estuary-materializations 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.
What it actually says
{
"name": "estuary-materializations",
"description": "Materialization skills for PostgreSQL, Snowflake, BigQuery, Redshift, Databricks, ClickHouse, HubSpot, and any destination connector",
"source": "./",
"strict": false,
"skills": [
"./skills/materialize-postgres-create",
"./skills/materialize-snowflake-create",
"./skills/materialize-bigquery-create",
"./skills/materialize-redshift-create",
"./skills/materialize-databricks-create",
"./skills/materialize-clickhouse-create",
"./skills/materialize-hubspot-create",
"./skills/materialize-generic-create"
]
}What it installs
The manifest is a name and a version. 8 skills travel with it, and installing the plugin installs all of them — 532 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill materialize-hubspot-create A 78 tokens
- Skill materialize-clickhouse-create A 64 tokens
- Skill materialize-databricks-create A 76 tokens
- Skill materialize-snowflake-create A 65 tokens
- Skill materialize-bigquery-create A 64 tokens
- Skill materialize-generic-create A 56 tokens
- Skill materialize-postgres-create A 64 tokens
- Skill materialize-redshift-create A 65 tokens
What ships with it
1 file beside marketplace.json#estuary-materializations 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.
- 1mo ago Changed · +1 lines 89d1ef4a5472
- 1mo ago First seen · 15 lines scan A 120cb01cd4e5
estuary-materializations is a plugin published in the GitHub repository estuary/agent-skills (7 stars, last pushed 26d ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-09-03.
Other plugins, from other repositories
dbconvert-streams
Read-only SQL across your PostgreSQL, MySQL, S3 buckets and local data files — one query can join across all of them.
polygres
Use Polygres MCP, sync PostgreSQL sources, set up data pipelines and embeddings, build retrieval, and troubleshoot through supported dashboard, CLI, SDK, and Runtime API workflows.
LUXOR Database Pro
Professional database engineering skills covering PostgreSQL, SQLAlchemy, Alembic, pandas, Redis, vector databases, and database patterns.
pgvector-stack
A minimal PostgreSQL container with pgvector, an extension for storing and searching numerical representations of data. It provides shared database infrastructure for other plugins.
cloud-sql-postgresql
Create, connect, and interact with a Cloud SQL for PostgreSQL database and data.
database-manager
Comprehensive database management with PostgreSQL/MySQL support, migrations, and query optimization.