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.
/plugin marketplace add estuary/agent-skillsnpx agentmods add plugins/estuary/agent-skills/estuary-schemagit 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-schema)<a href="https://agentmods.dev/plugins/estuary/agent-skills/estuary-schema"><img src="https://agentmods.dev/badge/plugins/estuary/agent-skills/estuary-schema.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
estuary-schema 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.
What it actually says
{
"name": "estuary-schema",
"description": "Schema modification skills for Estuary collections and materializations: projections, field selection, custom column types, redaction, null defaults, and defining fields",
"source": "./",
"strict": false,
"skills": [
"./skills/schema-projections",
"./skills/schema-field-selection",
"./skills/schema-custom-types-ddl",
"./skills/schema-field-redaction",
"./skills/schema-null-defaults",
"./skills/schema-define-fields"
]
}What it installs
The manifest is a name and a version. 6 skills travel with it, and installing the plugin installs all of them — 491 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside marketplace.json#estuary-schema 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 · 14 lines scan A 9fb0598cbf77
estuary-schema is a plugin published in the GitHub repository estuary/agent-skills (7 stars, last pushed 15d 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
migrate-tool
Generate database migrations and code migration scripts for framework upgrades.
butterbase-skills
Build full-stack apps with Butterbase — AI-Native Backend-as-a-Service. Skills for app creation, schema design, frontend deployment, RLS debugging, serverless functions, and contributing.
data-scientist
Data analysis expert for SQL queries, BigQuery operations, and data insights. Use proactively for data analysis tasks and queries.
cdc-health-mcp-server
Search and query CDC public health data — mortality, vaccinations, surveillance, behavioral risk (Socrata SODA API) via MCP. STDIO or Streamable HTTP.
sql-database-pipeline
Build SQL database pipelines with dlt: connect to any SQL source, load tables to a destination, tune performance with backends.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.