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-statusgit 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-status)<a href="https://agentmods.dev/skills/estuary/agent-skills/estuary-catalog-status"><img src="https://agentmods.dev/badge/skills/estuary/agent-skills/estuary-catalog-status/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-status"><img src="https://agentmods.dev/badge/skills/estuary/agent-skills/estuary-catalog-status.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.00154 | $0.02119 |
| Opus 5 | $0.00077 | $0.01059 |
| Sonnet 5 | $0.00031 | $0.00424 |
| Haiku 4.5 | $0.00015 | $0.00212 |
Grade A, and why
estuary-catalog-status 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 11d 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
flowctl catalog status - Check status of Estuary resources
Concepts: The catalog contains all Estuary specs — captures, materializations, collections, derivations, and tests. The status command shows the current control-plane state including whether the task is running, its last failure, publication history, and shard health.
Note: This command shows control-plane status — whether the controller has activated the task, published specs, and received shard health reports. It does not directly poll data-plane (runtime) state in real time, so brief transient failures or throughput issues may not be reflected here. For real-time runtime behavior, use flowctl logs.
Prerequisites
flowctl auth login
Basic Usage
flowctl catalog status <task> --output json | jq
Check a task and everything connected to it (upstream/downstream collections and tasks):
flowctl catalog status <task> --connected --output json | jq
Listing connectors
catalog status targets a single named resource. To enumerate which connectors exist — e.g. "show me all my active connectors" — use flowctl catalog list instead.
Gotcha — the type flags are mutually exclusive. --captures, --materializations, --collections, and --tests are include filters and only one may be passed at a time. Combining them fails:
$ flowctl catalog list --captures --materializations
error: the argument '--captures' cannot be used with '--materializations'
The --captures=false negative form shown in --help is not accepted by the CLI (error: unexpected value 'false'), so you cannot exclude types that way either.
To get captures and materializations together, run catalog list with no type flags (which returns everything) and filter by type in jq:
# All ACTIVE (non-disabled) connectors — captures + materializations — in one call
flowctl catalog list -o json | jq -r '
select((.liveSpec.catalogType == "capture" or .liveSpec.catalogType == "materialization")
and .liveSpec.isDisabled != true)
| .catalogName + " [" + .liveSpec.catalogType + "] [" + (.status.type // "?") + "]"'
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.
- 11d ago First seen · 163 lines · 154 tokens per session scan A bd61aac5340c
estuary-catalog-status is a skill published in the GitHub repository estuary/agent-skills (7 stars, last pushed 21d ago), licensed Apache-2.0. It adds 154 tokens to every session and 2,119 once invoked, about $0.0008 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 writing an Apex change-event trigger — use apex/change-data-capture-apex. NOT for subscribing an external system over Pub/Sub or CometD — use…
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…
target-connector
This skill should be used when creating a new target connector for CocoIndex to integrate with external systems. It provides guidance on implementing TargetHandler, TargetActionSink, and related types for declarative target state synchronization with change detection and automatic cleanup.
cocoindex-diagrams
This skill should be used when creating, editing, or reviewing inline SVG diagrams for the CocoIndex docs site (anything under docs/src/content/docs/). It encodes the component-based primitive system under docs/src/components/diagrams/, the palette + shape semantics, the preview-and-verify loop using headless Chrome…