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/koappnpx skills add AxiosLeo/node-koapp --skill koappgit clone --depth 1 https://github.com/AxiosLeo/node-koappWhat 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.00086 | $0.01327 |
| Opus 5 | $0.00043 | $0.00664 |
| Sonnet 5 | $0.00017 | $0.00265 |
| Haiku 4.5 | $0.00009 | $0.00133 |
Grade A, and why
koapp 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.
How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
@axiosleo/koapp Framework Overview
@axiosleo/koapp is a Node.js framework built on top of Koa that provides three runtime modes (HTTP, TCP, WebSocket) behind a unified Application base, plus batteries-included helpers for routing, validation, response shaping, and Server-Sent Events.
Minimum Node.js version: 16.0.0.
Installation
npm install @axiosleo/koapp
Core Exports
All symbols below come from require('@axiosleo/koapp'):
| Symbol | Kind | When to use |
|---|---|---|
KoaApplication |
Class | Stand up an HTTP server on top of Koa |
SocketApplication |
Class | Stand up a TCP socket server (Node net) |
WebSocketApplication |
Class | Stand up a WebSocket server (the ws library) |
Application |
Class | Base class, rarely instantiated directly |
Router |
Class | Define routes, path params, validators, nested routers |
Controller |
Class | Base class to organize request handlers with response helpers |
Model |
Class | Structured validation (via validatorjs) + object serialization |
success / failed / result / response / error |
Functions | Throw-style response helpers consumed by the framework's workflow |
HttpError / HttpResponse |
Classes | Throwable error/response objects |
middlewares.KoaSSEMiddleware |
Factory | Attach a Server-Sent Events stream to a Koa route |
middlewares.KoaSessionMiddleware |
Re-export | koa-session for custom setups |
initContext |
Function | Advanced: build a framework context for custom transports |
Full quick-start example lives in quick-start.md.
Class Hierarchy
EventEmitter
└── Application (src/apps/app.js)
├── KoaApplication (src/apps/koa.js) - HTTP
└── SocketApplication (src/apps/socket.js) - TCP
└── WebSocketApplication (src/apps/websocket.js) - WebSocket
WebSocketApplication inherits all connection-management helpers
(send, close, sendByConnectionId, closeByConnectionId, getConnection,
ping, broadcast) from SocketApplication. Only the send, close, and
broadcast transport wrappers are overridden.
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.
- yesterday First seen · 118 lines · 86 tokens per session scan A 974207dd5419
koapp is a skill published in the GitHub repository AxiosLeo/node-koapp (129 stars, last pushed 18d ago), licensed MIT. It adds 86 tokens to every session and 1,327 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.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…