realtime-streaming

Rules for building applications that send ongoing updates as events happen, such as chat, collaboration, data processing, or video processing. They describe Motia Streams, which store structured data and serve it to subscribed clients.

In plain words
What is it for?
Use them when configuring a stream, defining its data schema with Zod or JSON Schema, setting storage, and letting clients subscribe to updates.
Why use it?
They provide a defined way to deliver asynchronous updates to clients during long-running or continuously changing work.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/crypticsaiyan/githubwrapped/realtime-streaming
Clone the repo
git clone --depth 1 https://github.com/crypticsaiyan/githubwrapped

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 2,548 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.02548
Opus 5 $0.00000 $0.01274
Sonnet 5 $0.00000 $0.00510
Haiku 4.5 $0.00000 $0.00255

Measured yesterday against content hash 9c4f1f25c5d7, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

realtime-streaming 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 yesterday.

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.

.cursor/rules/motia/realtime-streaming.mdc · 402 lines

How it starts

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

Real-time Streaming

Building event driven applications often requires some real-time streaming capabilities.

  • Like integration with LLMs, they should be implemented in an asynchronous way and updates should come in real-time.
  • Chat applications, real-time collaboration, etc.
  • Long living processes like data processing, video processing, etc.

Motia has a built-in real-time streaming system that allows you to easily implement real-time streaming capabilities in your application.

It's called Streams.

Stream Configuration

Creating a Stream means defining a data schema that will be stored and served to the clients who are subscribing.

StreamConfig Type Definition

export type ZodInput = ZodObject<any> | ZodArray<any>
export type StepSchemaInput = ZodInput | JsonSchema

export type StreamSubscription = { groupId: string; id?: string }

export interface StreamConfig {
  /**
   * The stream name, used on the client side to subscribe.
   */
  name: string

  /**
   * Schema for stream data. Accepts either:
   * - Zod schema (ZodObject or ZodArray)
   * - JSON Schema object
   */
  schema: StepSchemaInput

  /**
   * Storage configuration for the stream.
   * Use 'default' for built-in storage or 'custom' with a factory function.
   */
  baseConfig: { storageType: 'default' } | { storageType: 'custom'; factory: () => MotiaStream<any> }

  /**
   * Optional: Access control callback to authorize subscriptions.
   * Return true to allow access, false to deny.
   */
  canAccess?: (subscription: StreamSubscription, authContext: any) => boolean | Promise<boolean>
}

TypeScript Example

// steps/streams/chat-messages.stream.ts
import { StreamConfig } from 'motia'
import { z } from 'zod'

export const chatMessageSchema = z.object({
  id: z.string(),
  userId: z.string(),
  message: z.string(),
  timestamp: z.string()
})

export type ChatMessage = z.infer<typeof chatMessageSchema>

export const config: StreamConfig = {
  name: 'chatMessage',
  schema: chatMessageSchema,
  baseConfig: { storageType: 'default' },
}

Read the full file on GitHub · 402 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. yesterday First seen · 402 lines · 0 tokens per session scan A 9c4f1f25c5d7

Subscribe to this mod's changes

realtime-streaming is a cursor rule published in the GitHub repository crypticsaiyan/githubwrapped (5 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,548 tokens. 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.