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 skills add jkaninda/okapi-skills --skill sse_streamgit clone --depth 1 https://github.com/jkaninda/okapi-skillsWrote 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/jkaninda/okapi-skills/sse_stream)<a href="https://agentmods.dev/skills/jkaninda/okapi-skills/sse_stream"><img src="https://agentmods.dev/badge/skills/jkaninda/okapi-skills/sse_stream/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/skills/jkaninda/okapi-skills/sse_stream"><img src="https://agentmods.dev/badge/skills/jkaninda/okapi-skills/sse_stream.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.01445 |
| Opus 5 | $0.00000 | $0.00723 |
| Sonnet 5 | $0.00000 | $0.00289 |
| Haiku 4.5 | $0.00000 | $0.00145 |
Grade A, and why
sse_stream 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 9d 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 — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Okapi SSE (Server-Sent Events) Skills
Okapi provides built-in SSE support for real-time server-to-client streaming over HTTP. SSE connections are long-lived GET requests where the server pushes events using the text/event-stream content type. The framework handles headers, flushing, keep-alive pings, and serialization automatically.
Core Types
| Type | Description |
|---|---|
Message |
Single SSE message with ID, Event, Data, Retry, Serializer fields |
StreamOptions |
Advanced stream config: Serializer, PingInterval, OnError callback |
Serializer |
Interface: Serialize(data any) (string, error) — custom data encoding |
SendFunc |
func(data any, eventType string) (string, error) |
Built-in Serializers
| Serializer | Description |
|---|---|
okapi.JSONSerializer |
Default — marshals data as JSON |
okapi.TextSerializer |
Plain text via fmt.Sprintf("%v", data) |
okapi.Base64Serializer |
Base64-encodes []byte data |
Sending Single Events
// Fire-and-forget event (no ID, auto-generated internally)
c.SSEvent("message", data)
// Event with explicit ID
c.SSESendEvent("event-1", "message", data)
// Data-only (no event type)
c.SSESendData(data)
// Explicit serializer variants
c.SSESendJSON(data) // JSON serializer
c.SSESendText("hello") // Text serializer
c.SSESendBinary([]byte{...}) // Base64 serializer
c.SendSSECustom(data, mySerializer) // Custom serializer
c.SendSSEvent(id, eventType, data)is deprecated — usec.SSESendEvent(...).
Each helper writes the frame and flushes it, so events reach the client immediately. okapi.LoggerMiddleware skips SSE requests, keeping long-lived streams out of the access log.
A Message can also be written directly to any http.ResponseWriter:
msg := okapi.Message{Event: "update", Data: payload}
id, err := msg.Send(c.Response()) // writes the frame, returns the message ID
err = msg.Close(c.Response()) // flush
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.
- 9d ago First seen · 206 lines · 0 tokens per session scan A dd24e65ab1f5
sse_stream is a skill published in the GitHub repository jkaninda/okapi-skills (3 stars, last pushed 24d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,445 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 skills, from other repositories
webhook-setup
Set up webhook receivers with signature verification, idempotent event processing, retry handling, and dead letter queues for reliable event-driven integrations. Use when the user requests webhook setup or provides relevant inputs for this workflow.
graphql-api-design
Design GraphQL APIs with well-structured schemas, efficient resolvers, pagination, and performance patterns like DataLoader and federation. Use when the user requests graphql api design or provides relevant inputs for this workflow.
oauth-2-0-setup
Implement OAuth 2.0 authentication flows including authorization code with PKCE, client credentials, and device code for secure API integration. Use when the user requests oauth 2 0 setup or provides relevant inputs for this workflow.
api-design
Design RESTful APIs with proper resource modeling, HTTP method semantics, status codes, pagination, versioning, and documentation. Use when the user requests api design or provides relevant inputs for this workflow.
api-integration
Integrate with external APIs using REST clients, webhook consumers, SDK wrappers, and polling patterns with proper authentication, error handling, and retry logic. Use when the user requests api integration or provides relevant inputs for this workflow.
dynamic-application-security-testing
Perform dynamic security testing against running web applications and APIs to discover vulnerabilities through active probing and fuzzing. Use when the user requests dynamic application security testing or provides relevant inputs for this workflow.