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.
git clone --depth 1 https://github.com/crypticsaiyan/githubwrappedWrote 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/rules/crypticsaiyan/githubwrapped/realtime-streaming)<a href="https://agentmods.dev/rules/crypticsaiyan/githubwrapped/realtime-streaming"><img src="https://agentmods.dev/badge/rules/crypticsaiyan/githubwrapped/realtime-streaming/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/rules/crypticsaiyan/githubwrapped/realtime-streaming"><img src="https://agentmods.dev/badge/rules/crypticsaiyan/githubwrapped/realtime-streaming.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.00000 | $0.02548 |
| Opus 5.5 | $0.00000 | $0.01019 |
| Sonnet 5.5 | $0.00000 | $0.00510 |
| Haiku 4.5 | $0.00000 | $0.00255 |
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 1mo 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 — 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' },
}
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.
- 1mo ago First seen · 402 lines · 0 tokens per session scan A 9c4f1f25c5d7
realtime-streaming is a cursor rule published in the GitHub repository crypticsaiyan/githubwrapped (5 stars, last pushed 9mo 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.
Other cursor rules, from other repositories
api-property-optionality-hygiene
Fix ApiProperty/ApiPropertyOptional optionality mismatches in DTO files; use for scheduled batch fixes or DTO edits.
django
Definitive guidelines for writing maintainable, performant, and secure Django applications, emphasizing modern best practices, clear code organization, and efficient patterns.
env-validation-gate
Env validation gate — every app with ≥1 required env var validates its contract at boot via Zod; raw process.env is banned outside the env module. Full pattern in .claude/skills/t2000-env-gate/.
php-client-implementation
Guidelines for implementing MCP clients in PHP.
api-patterns
A set of API and NestJS patterns for the buero.de backend.
android-networking-retrofit-okhttp
Build Android networking stacks with Retrofit, OkHttp, interceptors, API contracts, and resilient error handling.