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/kouroshez/coding-os/realtime-websocketsnpx skills add kouroshez/coding-os --skill realtime-websocketsgit clone --depth 1 https://github.com/kouroshez/coding-osWrote 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/kouroshez/coding-os/realtime-websockets)<a href="https://agentmods.dev/skills/kouroshez/coding-os/realtime-websockets"><img src="https://agentmods.dev/badge/skills/kouroshez/coding-os/realtime-websockets.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.00193 | $0.02718 |
| Opus 5 | $0.00097 | $0.01359 |
| Sonnet 5 | $0.00039 | $0.00544 |
| Haiku 4.5 | $0.00019 | $0.00272 |
Grade A, and why
realtime-websockets 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 5d 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Realtime — WebSockets + Server-Sent Events
A practical guide to running persistent realtime connections in production. Stack-agnostic; concrete patterns reference ws/Socket.IO (Node), websockets/Starlette (Python), gorilla/websocket + melody (Go), and Redis/NATS as the fan-out bus.
When to Use This Skill
- Adding live updates: chat, notifications, presence, collaborative editing, live dashboards, order/status streams.
- Choosing between WebSocket, Server-Sent Events (SSE), and long-polling.
- Debugging dropped connections, zombie sockets, or "the client thinks it's connected but messages stop arriving".
- Implementing reliable reconnection (backoff, resume, missed-message replay).
- Scaling a socket server beyond one process/node (fan-out across instances).
- Authenticating and authorizing a connection at the upgrade handshake.
Skip when: the interaction is request/response (use HTTP — that is api-design), or the question is the schema of subscription payloads (that is graphql for graphql-ws).
Boundary — Realtime vs api-design vs graphql
| Concern | Owner |
|---|---|
| REST/GraphQL request-response contracts, versioning, idempotency keys, RFC 9457 HTTP errors | api-design |
| The persistent connection after upgrade: lifecycle, heartbeat, reconnect, backpressure, fan-out, presence | realtime-websockets (this skill) |
The schema/shape of messages flowing over a graphql-ws subscription |
graphql |
api-design governs everything up to (and including) the HTTP request that opens the socket — the Upgrade handshake is an HTTP request and its auth/error semantics follow api-design. Once the connection is established and bidirectional, this skill takes over. Message payload schemas belong to whoever owns the domain (graphql for GraphQL subscriptions, or a plain JSON envelope this skill defines).
Transport Decision — WebSocket vs SSE vs Long-Poll
| Transport | Direction | Reconnect | Use when | Avoid when |
|---|---|---|---|---|
SSE (text/event-stream) |
server → client only | built-in (Last-Event-ID, auto-retry) |
server-push only: notifications, live feeds, log tails, LLM token streams | the client must also push frequently |
| WebSocket | full duplex | manual (build it) | chat, collaboration, gaming, anything bidirectional and chatty | a one-way feed where SSE's simplicity wins |
| Long-poll | request/response | n/a | last-resort fallback where WS/SSE are blocked by middleboxes | anything modern can do — it is a fallback, not a 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.
- 5d ago First seen · 153 lines · 193 tokens per session scan A 5a8289ecd205
realtime-websockets is a skill published in the GitHub repository kouroshez/coding-os (6 stars, last pushed 5d ago), licensed Apache-2.0. It adds 193 tokens to every session and 2,718 once invoked, about $0.0010 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
graph-mutation-plan
Cookbook for composing an applygraphmutations plan — stable entitykey patterns, the canonical label/edge vocabulary, evidence/invalidation/confidence discipline, and a worked example. Load this when building a non-trivial mutation plan.
potpie-infra-architecture
Use for project infra and architecture context: environments, adapters, runtime configuration, deployments, service dependencies, datastores, API contracts, ownership, incidents, and dependency blast radius.
alfworld-receptacle-finder
Searches for a suitable empty or appropriately occupied receptacle (like a shelf or table) to place an object. Use when you are holding an object that needs to be stored or placed and must find a receptacle that meets the placement criteria. Examines candidate receptacles by navigating to and inspecting each one until…
alfworld-search-pattern-executor
Systematically searches a sequence of likely locations for a target object based on common sense. Use when you need to find a specific object and know which receptacles to check but not which one contains it. Takes a list of candidate receptacles, orchestrates navigation and inspection, and outputs when the target is…
ux-ui-analyze-single-page
Analyze exactly one captured UI page (from uxuimap screenshots + request JSON) and immediately write/update uxuimap/pages/{page}.md in neutral descriptive language. Use when asked to analyze screenshots, rewrite corresponding analysis immediately, or avoid memory/context saturation.
scienceworld-growth-focuser
Use when you have planted a seed or need to track a plant's growth stage (sprouting, flowering, reproduction). Applies the 'focus on' action to a specific plant or biological entity to signal intent and monitor its development. Trigger after planting or when you need to observe life cycle progression in the…