estuary-catalog-history

estuary-catalog-history is a skill for Claude Code from estuary/agent-skills. It costs 83 tokens per session (3,005 once invoked), scanned A, original, Apache-2.0.

A view of the publication history for an Estuary catalog resource, such as a capture, collection, or materialization. Each entry records when a change was published, who made it, and what the resource definition was then.

In plain words
What is it for?
Use it to see what changed, identify who changed it, review earlier specifications, and compare changes across data pipelines.
Why use it?
It provides a timeline for finding configuration changes and connecting a new problem with an earlier edit. Full resource definitions can be included when needed.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the estuary-operations plugin — 8 skills shipped together

Good fit Use it to see what changed, identify who changed it, review earlier specifications, and compare changes across data pipelines.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/estuary/agent-skills/estuary-catalog-history
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 estuary/agent-skills --skill estuary-catalog-history
Clone the repo
git clone --depth 1 https://github.com/estuary/agent-skills

Made for: Claude Code.

Or install estuary-operations, the plugin that ships this one along with the rest of its 8 skills.

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 estuary-catalog-history

README.md
[![agentmods](https://agentmods.dev/badge/skills/estuary/agent-skills/estuary-catalog-history/github.svg)](https://agentmods.dev/skills/estuary/agent-skills/estuary-catalog-history)
Your own site
<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.

agentmods 80×15 button for estuary-catalog-history

Your own site · 80×15
<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>
Per session 83 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.
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.00083 $0.03005
Opus 5 $0.00042 $0.01503
Sonnet 5 $0.00017 $0.00601
Haiku 4.5 $0.00008 $0.00300

Measured 12d ago against content hash 8de1a2af61cc, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

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.

skills/estuary-catalog-history/SKILL.md · 251 lines

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 name
  • catalog_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 entry
  • publication.publishedAt — ISO 8601 timestamp
  • publication.userEmail — who published
  • publication.userFullName — display name of publisher
  • publication.userId — UUID of publisher
  • publication.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"}}

Read the full file on GitHub · 251 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. 12d ago First seen · 251 lines · 83 tokens per session scan A 8de1a2af61cc

Subscribe to this mod's changes

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.

Related

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).

BanibrataChatterjee/AwesomeSalesforceSkills · 50 tokens

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…

bookforge-ai/bookforge-skills · 240 tokens

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…

cocoindex-io/cocoindex · 88 tokens

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.

confluentinc/agent-skills · 60 tokens

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…

confluentinc/agent-skills · 234 tokens

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…

confluentinc/agent-skills · 189 tokens