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 derivation-filter-transformgit 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/derivation-filter-transform)<a href="https://agentmods.dev/skills/estuary/agent-skills/derivation-filter-transform"><img src="https://agentmods.dev/badge/skills/estuary/agent-skills/derivation-filter-transform.svg" alt="Measured on agentmods" 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.00123 | $0.03339 |
| Opus 5 | $0.00062 | $0.01670 |
| Sonnet 5 | $0.00025 | $0.00668 |
| Haiku 4.5 | $0.00012 | $0.00334 |
Grade A, and why
derivation-filter-transform 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 7d 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 — 256 lines — stays where its author put it; the contents beside it link to each section on GitHub.
derivation-filter-transform
Stateless Estuary derivation that filters documents and/or transforms field values. Each source document produces zero or one output document; no state, no cross-document coordination.
Prereq: read derivation-basics first for concepts, project layout, workflow, and language choice.
When to use this over alternatives
- Filtering (
WHEREclause): drop documents that don't match criteria - Computed fields: derive new fields from existing ones (
CASE, arithmetic, string manipulation, lookups) - Data cleansing: normalise formats, trim whitespace, replace nulls
- Selecting a subset of fields when combined with the above
For a plain rename or nested-field flattening with no computation, use schema-projections — a projection doesn't require a derivation task.
Canonical Example — SQL
Cleanse a customers collection for downstream analytics: drop inactive accounts and those with obviously invalid emails, normalise the email, and compute a tier bucket from lifetime spend.
schema.yaml
The writeSchema (what the lambda must emit). Enum constraints on tier are enforced at write time; the readSchema (in flow.yaml below) layers in inference for everything else. See derivation-basics § Schema setup.
type: object
properties:
customer_id:
type: string
email_normalized:
type: string
signup_date:
type: string
format: date
tier:
type: string
enum: [bronze, silver, gold]
required: [customer_id, email_normalized, tier]
flow.yaml
collections:
acmeCo/analytics/active-customers:
writeSchema: schema.yaml
readSchema:
allOf:
- $ref: flow://write-schema
- $ref: flow://inferred-schema
key: [/customer_id]
derive:
using:
sqlite: {}
transforms:
- name: cleanseCustomers
source: acmeCo/production/customers
shuffle: any
lambda: |
SELECT
$id AS customer_id,
LOWER(TRIM($email)) AS email_normalized,
date($created_at) AS signup_date,
CASE
WHEN $lifetime_spend >= 10000 THEN 'gold'
WHEN $lifetime_spend >= 1000 THEN 'silver'
ELSE 'bronze'
END AS tier
WHERE $status = 'active'
AND $email LIKE '%@%';
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.
- 7d ago First seen · 256 lines · 123 tokens per session scan A 5b84c740970d
derivation-filter-transform is a skill published in the GitHub repository estuary/agent-skills (7 stars, last pushed 16d ago), licensed Apache-2.0. It adds 123 tokens to every session and 3,339 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 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…