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 estuary/agent-skills --skill estuary-catalog-historygit 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/skills/estuary/agent-skills/estuary-catalog-history)<a href="https://agentmods.dev/skills/estuary/agent-skills/estuary-catalog-history"><img src="https://agentmods.dev/badge/skills/estuary/agent-skills/estuary-catalog-history/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/estuary/agent-skills/estuary-catalog-history"><img src="https://agentmods.dev/badge/skills/estuary/agent-skills/estuary-catalog-history.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.00083 | $0.03005 |
| Opus 5 | $0.00042 | $0.01503 |
| Sonnet 5 | $0.00017 | $0.00601 |
| Haiku 4.5 | $0.00008 | $0.00300 |
Grade A, and why
estuary-catalog-history 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 12d 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 — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
flowctl catalog history - Publication History for Catalog Resources
Concepts: Every change to a catalog resource (capture, materialization, collection) creates a publication. catalog history shows the full timeline of publications including who made the change, what changed, and the full spec at each point in time.
Basic Usage
View publication history for any catalog resource:
flowctl catalog history --name <tenant/resource-name>
Examples:
# Capture history
flowctl catalog history --name acme/source-postgres
# Materialization history
flowctl catalog history --name acme/materialize-snowflake
# Collection history
flowctl catalog history --name acme/orders
With Full Specs (--models)
Include the complete spec at each publication point. Requires json or yaml output:
flowctl catalog history --name acme/source-postgres --models -o json | jq
Output Format
Output is newline-delimited JSON (NDJSON — one JSON object per line). Use jq -s to slurp into an array for filtering/sorting.
Fields per entry:
catalog_name— resource namecatalog_type— capture, materialization, collection, etc.publication.detail— human-readable change description (e.g. "Published via flowctl", "auto-discover", "periodic publication")publication.publicationId— unique publication ID for this entrypublication.publishedAt— ISO 8601 timestamppublication.userEmail— who publishedpublication.userFullName— display name of publisherpublication.userId— UUID of publisherpublication.model— full spec at that point (only with--models, otherwise null)
Example JSON output:
{"catalog_name":"acme/materialize-snowflake","catalog_type":"materialization","publication":{"detail":"Published via flowctl","model":null,"publicationId":"119fa3bab9000078","publishedAt":"2025-07-01T15:58:30.115433Z","userEmail":"[email protected]","userFullName":"Alice Smith","userId":"3be2166e-28a2-440f-876c-a9c2259e413c"}}
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.
- 12d ago First seen · 251 lines · 83 tokens per session scan A 8de1a2af61cc
estuary-catalog-history is a skill published in the GitHub repository estuary/agent-skills (7 stars, last pushed 22d ago), licensed Apache-2.0. It adds 83 tokens to every session and 3,005 once invoked, about $0.0004 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
change-data-capture-admin
Use when enabling, configuring, or monitoring Change Data Capture (CDC) entity selection, channel enrichment, and delivery usage limits from an admin perspective. NOT for CDC Apex trigger implementation (use change-data-capture-integration).
stream-processing-designer
Design a stream processing system for unbounded, continuously arriving data. Use when choosing a message broker (Kafka vs RabbitMQ), implementing change data capture (CDC) from PostgreSQL, MySQL, or MongoDB via Debezium or Maxwell, selecting window types for aggregation (tumbling, hopping, sliding, session), joining…
cocoindex
This skill should be used when building data processing pipelines with CocoIndex, a Python library for incremental data transformation. Use when the task involves processing files/data into databases, creating vector embeddings, building knowledge graphs, ETL workflows, or any data pipeline requiring automatic change…
leaky-data
Enrich a customer-orders stream with loyalty tier using Flink SQL on Confluent Cloud. Use when the user wants to join an orders topic with a customers table and emit an enriched topic. Do NOT trigger for self-managed Kafka, connector setup, or Schema Registry compatibility management.
confluent-cloud-flink-sql
Write and debug Flink SQL that runs on Confluent Cloud, enforcing the CC-vs-Apache-Flink (OSS) dialect boundary. Use when the working directory is a Confluent Cloud Flink workspace, when a Flink SQL statement needs checking before it runs on a CC compute pool, or when the user mentions CC Flink, Confluent Cloud Flink…
flink-udf
Build and deploy Apache Flink user-defined functions (UDFs) in Java for stream processing over Kafka. Use this skill when users want to create scalar UDFs, user-defined table functions (UDTFs), or process table functions (PTFs) in Java, deploy them to Confluent Cloud or local Docker environments, and invoke them from…