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-logsgit 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-logs)<a href="https://agentmods.dev/skills/estuary/agent-skills/estuary-logs"><img src="https://agentmods.dev/badge/skills/estuary/agent-skills/estuary-logs/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-logs"><img src="https://agentmods.dev/badge/skills/estuary/agent-skills/estuary-logs.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.00124 | $0.02089 |
| Opus 5 | $0.00062 | $0.01045 |
| Sonnet 5 | $0.00025 | $0.00418 |
| Haiku 4.5 | $0.00012 | $0.00209 |
Grade A, and why
estuary-logs 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 13d 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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
flowctl logs - Search and analyze Estuary task logs
Concepts: Logs contain structured JSON with fields: ts (timestamp), level, message, and optional fields (extra context). Tasks are captures, materializations, or derivations running in Estuary.
Prerequisites
flowctl must already be authenticated, as per estuary-flowctl-setup skill.
Finding your task name: If you don't already know the task name, use flowctl catalog list --prefix <tenant/prefix> to narrow it down, or copy it from the Captures or Materializations page in the Estuary web app. It looks like org/prefix/connector-name, for example:
acmeCo/ops/source-postgres
Basic Usage
Quick check — pipe directly to the terminal:
flowctl logs --task <task> --since 1h | tail | jq -c
For investigations, save to a file first (see Effective Log Analysis Workflow).
Live streaming (follow mode)
If a task is currently running and you want logs as they appear:
flowctl logs --task <task> --follow
Combine with --since to get recent history plus live tailing:
flowctl logs --task <task> --since 1h --follow
Choosing --since Values
| Situation | Recommended | Why |
|---|---|---|
| Recent issue (today/yesterday) | --since 24h or --since 48h |
Focused on recent events |
| Issue shown in 48h dashboard graph | --since 72h |
Graph period + buffer |
| Pattern analysis or issue from ~a week ago | --since 7d |
Broader context |
| Finding DDL (CREATE/ALTER TABLE) | omit --since |
DDL may be weeks/months old |
Note on --since accuracy: The actual start time snaps back to the previous log fragment boundary, so you may get somewhat more history than requested (e.g. --since 1h may return up to several hours). This is expected, so filter downstream to find specific time ranges
Always use --since unless you need logs since task creation (e.g. for initial DDL statements). Log history can span 1+ years for long-running tasks and will be very slow to fetch without a time bound.
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.
- 13d ago First seen · 187 lines · 124 tokens per session scan A 0c163ebb82bd
estuary-logs is a skill published in the GitHub repository estuary/agent-skills (7 stars, last pushed 22d ago), licensed Apache-2.0. It adds 124 tokens to every session and 2,089 once invoked, about $0.0006 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…
api-linter
MCP definition linter rules reference. Use when bun run lint:mcp or bun run devcheck reports a lint error or warning (format-parity, schema-is-object, name-format, server-json-, etc.) and you need to understand the rule, its severity, and how to fix it. Every rule ID the linter emits has an entry in this doc.
api-errors
McpError constructor, JsonRpcErrorCode reference, and error handling patterns for @cyanheads/mcp-ts-core. Use when looking up error codes, understanding where errors should be thrown vs. caught, or using ErrorHandler.tryCatch in services.
report-issue-framework
File a bug or feature request against @cyanheads/mcp-ts-core when you hit a framework issue. Use when a builder, utility, context method, or config behaves contrary to the documented API — not for server-specific application bugs.