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/axiosleo/node-koapp/koapp-ssenpx skills add AxiosLeo/node-koapp --skill koapp-ssegit clone --depth 1 https://github.com/AxiosLeo/node-koappWrote 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/axiosleo/node-koapp/koapp-sse)<a href="https://agentmods.dev/skills/axiosleo/node-koapp/koapp-sse"><img src="https://agentmods.dev/badge/skills/axiosleo/node-koapp/koapp-sse.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 | $0.00077 | $0.01552 |
| Opus 5 | $0.00039 | $0.00776 |
| Sonnet 5 | $0.00015 | $0.00310 |
| Haiku 4.5 | $0.00008 | $0.00155 |
Grade A, and why
koapp-sse 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 4d 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 — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
@axiosleo/koapp Server-Sent Events Middleware
Source: src/middlewares/sse.js.
KoaSSEMiddleware upgrades a Koa request to a Server-Sent Events (SSE)
stream, setting the right headers and exposing ctx.sse.send(...) for
pushing events to the browser over plain HTTP.
Use SSE when:
- You need server → client streaming (notifications, logs, live charts)
- You do NOT need client → server streaming (use koapp-apps WebSocket instead)
- You want a simple, proxy-friendly transport - SSE works over HTTP/1.1
Browsers reconnect automatically; most reverse proxies handle it fine.
Import
const { KoaSSEMiddleware } = require('@axiosleo/koapp').middlewares;
Middleware factory
const middleware = KoaSSEMiddleware({
pingInterval: 60000, // ms between heartbeat comments (default 60s)
closeEvent: 'close' // event name sent on stream close
});
The factory returns a standard Koa middleware (ctx, next) => {}.
Wiring into a router handler
Because the framework already dispatches routes via its workflow, invoke
the middleware inside the handler, passing context.koa:
const { Router } = require('@axiosleo/koapp');
const { KoaSSEMiddleware } = require('@axiosleo/koapp').middlewares;
const router = new Router('/');
router.any('/sse', async (context) => {
const sse = KoaSSEMiddleware();
await sse(context.koa, async () => {});
context.koa.sse.send({ data: 'hello, world!' });
process.nextTick(async () => {
for (let i = 0; i < 5; i++) {
context.koa.sse.send({ id: i, event: 'tick', data: { i } });
await new Promise((r) => setTimeout(r, 1000));
}
context.koa.sse.close();
});
});
Key points:
- Call
await sse(context.koa, async () => {})- pass a no-opnext. - After that,
context.koa.sseexists. - Push events with
context.koa.sse.send(event); end with.close(). - Do not call
success / failed / resultin the same handler - SSE takes over the response body.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 204 lines · 77 tokens per session scan A fb79edb93c6e
koapp-sse is a skill published in the GitHub repository AxiosLeo/node-koapp (145 stars, last pushed 20d ago), licensed MIT. It adds 77 tokens to every session and 1,552 once invoked, about $0.0004 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…