streaming-data

streaming-data is a skill for Claude Code from ancoleman/ai-design-components. It costs 68 tokens per session (2,553 once invoked), scanned A, original, MIT.

A guide to moving and processing data as events arrive, using systems such as Kafka, Pulsar, Flink, and Spark. It covers message brokers, stream processing, event sourcing, and change data capture, which records database changes as events.

In plain words
What is it for?
Use it for real-time analytics, microservice communication, log and metrics pipelines, IoT systems, and data integration.
Why use it?
It helps build systems that react to new data quickly and reliably instead of waiting for periodic batch jobs.

Skill for Claude Code

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

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python scripts/validate-kafka-config.py --config producer.yaml.

Part of the data-engineering-skills plugin — 6 skills shipped together

Good fit Use it for real-time analytics, microservice communication, log and metrics pipelines, IoT systems, and data integration.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/ancoleman/ai-design-components
agentmods
npx agentmods add skills/ancoleman/ai-design-components/streaming-data

Made for: Claude Code.

Or install data-engineering-skills, the plugin that ships this one along with the rest of its 6 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 streaming-data

README.md
[![agentmods](https://agentmods.dev/badge/skills/ancoleman/ai-design-components/streaming-data/github.svg)](https://agentmods.dev/skills/ancoleman/ai-design-components/streaming-data)
Your own site
<a href="https://agentmods.dev/skills/ancoleman/ai-design-components/streaming-data"><img src="https://agentmods.dev/badge/skills/ancoleman/ai-design-components/streaming-data/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 streaming-data

Your own site · 80×15
<a href="https://agentmods.dev/skills/ancoleman/ai-design-components/streaming-data"><img src="https://agentmods.dev/badge/skills/ancoleman/ai-design-components/streaming-data.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 68 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,553 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.00068 $0.02553
Opus 5 $0.00034 $0.01277
Sonnet 5 $0.00014 $0.00511
Haiku 4.5 $0.00007 $0.00255

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

Security

Grade A, and why

streaming-data 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.

The scan reads SKILL.md. This mod also ships 2 executable files (examples/python/basic_consumer.py, examples/typescript/basic-producer.ts), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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/streaming-data/SKILL.md · 362 lines

How it starts

The opening of the file, as written. The whole thing — 362 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Streaming Data Processing

Build production-ready event streaming systems and real-time data pipelines using modern message brokers and stream processors.

When to Use This Skill

Use this skill when:

  • Building event-driven architectures and microservices communication
  • Processing real-time analytics, monitoring, or alerting systems
  • Implementing data integration pipelines (CDC, ETL/ELT)
  • Creating log or metrics aggregation systems
  • Developing IoT platforms or high-frequency trading systems

Core Concepts

Message Brokers vs Stream Processors

Message Brokers (Kafka, Pulsar, Redpanda):

  • Store and distribute event streams
  • Provide durability, replay capability, partitioning
  • Handle producer/consumer coordination

Stream Processors (Flink, Spark, Kafka Streams):

  • Transform and aggregate streaming data
  • Provide windowing, joins, stateful operations
  • Execute complex event processing (CEP)

Delivery Guarantees

At-Most-Once:

  • Messages may be lost, no duplicates
  • Lowest overhead
  • Use for: Metrics, logs where loss is acceptable

At-Least-Once:

  • Messages never lost, may have duplicates
  • Moderate overhead, requires idempotent consumers
  • Use for: Most applications (default choice)

Exactly-Once:

  • Messages never lost or duplicated
  • Highest overhead, requires transactional processing
  • Use for: Financial transactions, critical state updates

Quick Start Guide

Step 1: Choose a Message Broker

See references/broker-selection.md for detailed comparison.

Quick decision:

  • Apache Kafka: Mature ecosystem, enterprise features, event sourcing
  • Redpanda: Low latency, Kafka-compatible, simpler operations (no ZooKeeper)
  • Apache Pulsar: Multi-tenancy, geo-replication, tiered storage
  • RabbitMQ: Traditional message queues, RPC patterns

Step 2: Choose a Stream Processor (if needed)

See references/processor-selection.md for detailed comparison.

Quick decision:

  • Apache Flink: Millisecond latency, real-time analytics, CEP
  • Apache Spark: Batch + stream hybrid, ML integration, analytics
  • Kafka Streams: Embedded in microservices, no separate cluster
  • ksqlDB: SQL interface for stream processing

Read the full file on GitHub · 362 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. 7d ago First seen · 362 lines · 68 tokens per session scan A a932e0b4be68

Subscribe to this mod's changes

streaming-data is a skill published in the GitHub repository ancoleman/ai-design-components (517 stars, last pushed 9mo ago), licensed MIT. It adds 68 tokens to every session and 2,553 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-09-03.

Related

Other skills, from other repositories

serving-llms-vllm

Use when deploying production LLM APIs, optimizing inference latency/throughput, or serving models with limited GPU memory. Supports OpenAI-compatible endpoints, quantization (GPTQ/AWQ/FP8), and tensor parallelism.

NousResearch/hermes-agent · 27 tokens

omni-inference

The core OpenAI-compatible inference endpoints: chat completions, embeddings, images, audio (TTS/STT), moderations, rerank, and the Responses API. The primary integration surface for AI agents.

diegosouzapw/OmniRoute · 47 tokens

gemini-api-agent-platform

Guides the usage of the Gemini API on Agent Platform with the Google Gen AI SDK for enterprise AI applications. Covers SDK usage (Python, JS/TS, Go, Java, C#), capabilities like Live API, tools, multimedia generation, caching, and batch prediction.

davila7/claude-code-templates · 61 tokens

sglang

Fast structured generation and serving for LLMs with RadixAttention prefix caching. Use for JSON/regex outputs, constrained decoding, agentic workflows with tool calls, or when you need 5× faster inference than vLLM with prefix sharing. Powers 300,000+ GPUs at xAI, AMD, NVIDIA, and LinkedIn.

davila7/claude-code-templates · 72 tokens

data-engineering

Builds and operates data pipelines — ingestion, transformation, orchestration, quality testing, and reliability of data delivery. Use this to design or debug a pipeline, decide batch versus streaming, add data quality checks, handle late or duplicate data, or work out why a dashboard's numbers changed without anyone…

cbrock84/headcount · 67 tokens

form-strategy

Design forms that convert, validate well, resist spam, and integrate cleanly with downstream systems. Use this skill when designing or auditing any form (contact, signup, checkout, multi-step, embedded), planning validation logic, fighting spam, choosing form tooling, or improving form conversion. Triggers on form…

rampstackco/claude-skills · 107 tokens