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-appsnpx skills add AxiosLeo/node-koapp --skill koapp-appsgit 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.00078 | $0.01159 |
| Opus 5 | $0.00039 | $0.00580 |
| Sonnet 5 | $0.00016 | $0.00232 |
| Haiku 4.5 | $0.00008 | $0.00116 |
Grade A, and why
koapp-apps 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
@axiosleo/koapp Application Classes
@axiosleo/koapp exposes three runtime application classes, all extending a
shared Application base. Pick one based on the transport you need.
Which class do I need?
| Class | Transport | Use when |
|---|---|---|
KoaApplication |
HTTP(S) via Koa | REST APIs, file uploads, SSR, Server-Sent Events |
SocketApplication |
Raw TCP via Node net |
Custom TCP protocol, IoT gateways, line-delimited services |
WebSocketApplication |
WebSocket via ws |
Real-time browser apps, chat, live dashboards |
All three accept { port, routers, debug, app_id } at minimum; see the
per-class docs for full options:
- http-server.md -
KoaApplication - socket-server.md -
SocketApplication - websocket-server.md -
WebSocketApplication - examples.md - full server examples
Shared config keys
All three apps normalize config through Configuration from
@axiosleo/cli-tool:
{
port: 8080, // Port to listen on
listen_host: 'localhost', // '0.0.0.0' for public access (Koa only)
routers: [], // Array of Router instances
app_id: '', // Optional stable ID; auto uuid-v4 if empty
debug: false // Verbose logging
}
Shared events
All apps extend EventEmitter and emit:
starting- before the server bindsresponse- after each response is produced (framework uses this internally to write the response)
Socket apps also expose a separate app.event EventEmitter emitting:
connection- new client connectedlisten- server bound to the port
Shared lifecycle
const app = new KoaApplication({ ... });
app.on('starting', () => console.log('about to listen'));
await app.start(); // all three classes implement .start()
Connection management (Socket + WebSocket)
SocketApplication implements the following methods, inherited by
WebSocketApplication:
What ships with it
4 files 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 · 127 lines · 78 tokens per session scan A c74604bb239d
koapp-apps is a skill published in the GitHub repository AxiosLeo/node-koapp (129 stars, last pushed 18d ago), licensed MIT. It adds 78 tokens to every session and 1,159 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…