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 agentmods add skills/justanesta/claude-code-resources/data-eng-streaming-patternsnpx skills add justanesta/claude-code-resources --skill data-eng-streaming-patternsgit clone --depth 1 https://github.com/justanesta/claude-code-resourcesWrote 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/justanesta/claude-code-resources/data-eng-streaming-patterns)<a href="https://agentmods.dev/skills/justanesta/claude-code-resources/data-eng-streaming-patterns"><img src="https://agentmods.dev/badge/skills/justanesta/claude-code-resources/data-eng-streaming-patterns.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 | $0.00068 | $0.02270 |
| Opus 5 | $0.00034 | $0.01135 |
| Sonnet 5 | $0.00014 | $0.00454 |
| Haiku 4.5 | $0.00007 | $0.00227 |
Grade A, and why
data-eng-streaming-patterns 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 4d 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.
Streaming Data Patterns
Real-time data processing patterns for event-driven systems and streaming pipelines.
Core Principles
- Events are immutable facts -- Never mutate events in-flight; produce corrective events instead.
- Design for failure and replay -- Every component must handle reprocessing gracefully through idempotent writes and offset management.
- Exactly-once is a system property -- It emerges from idempotent producers, transactional writes, and deterministic processing combined.
- Backpressure over data loss -- When consumers fall behind, slow down producers or buffer intelligently rather than dropping messages.
- Schema evolution is mandatory -- Plan for backward and forward compatible schema changes from day one using a schema registry.
Apache Kafka Fundamentals
Kafka organizes data into topics split into partitions. Producers write by key for ordering; consumers read in groups for load balancing.
from confluent_kafka import Producer
import json
producer = Producer({
"bootstrap.servers": "broker1:9092,broker2:9092",
"enable.idempotence": True,
"acks": "all",
"compression.type": "lz4",
})
def produce_clickstream_event(user_id: str, event: dict):
"""Partition by user_id to preserve per-user ordering."""
producer.produce(
topic="clickstream-events",
key=user_id.encode("utf-8"),
value=json.dumps(event).encode("utf-8"),
callback=lambda err, msg: logger.error(f"Failed: {err}") if err else None,
)
producer.poll(0)
See kafka-patterns.md for:
- Consumer group configuration and rebalancing strategies
- Partitioning strategies for high-cardinality keys
- Exactly-once producer transactions
- Topic configuration and retention policies
Change Data Capture (CDC) Patterns
CDC captures row-level changes from database transaction logs, avoiding polling overhead.
# Debezium PostgreSQL connector
name: "orders-connector"
config:
connector.class: "io.debezium.connector.postgresql.PostgresConnector"
database.hostname: "postgres-primary"
database.dbname: "inventory"
table.include.list: "public.orders,public.customers"
plugin.name: "pgoutput"
slot.name: "debezium_slot"
tombstones.on.delete: true
snapshot.mode: "initial"
transforms: "route"
transforms.route.type: "org.apache.kafka.connect.transforms.RegexRouter"
transforms.route.regex: "([^.]+)\\.([^.]+)\\.([^.]+)"
transforms.route.replacement: "cdc.$3"
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 251 lines · 68 tokens per session scan A f97ca6477acb
data-eng-streaming-patterns is a skill published in the GitHub repository justanesta/claude-code-resources (2 stars, last pushed 4mo ago), licensed MIT. It adds 68 tokens to every session and 2,270 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…