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-controllernpx skills add AxiosLeo/node-koapp --skill koapp-controllergit 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.00061 | $0.01249 |
| Opus 5 | $0.00030 | $0.00624 |
| Sonnet 5 | $0.00012 | $0.00250 |
| Haiku 4.5 | $0.00006 | $0.00125 |
Grade A, and why
koapp-controller 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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
@axiosleo/koapp Controller
Source: src/controller.js.
Controller is a thin base class that mirrors the
response helpers as instance methods. Extend
it to keep related handlers together and share auxiliary state.
Import
const { Controller } = require('@axiosleo/koapp');
Instance API
| Method | Equivalent function | Notes |
|---|---|---|
this.success(data?, headers?) |
success(data, headers) |
200 OK JSON envelope |
this.failed(data?, code?, status?, headers?) |
failed(data, code, status, headers) |
Non-2xx JSON envelope |
this.result(data, status?, headers?) |
result(data, status, headers) |
Raw body pass-through |
this.response(data, code, status?, headers?) |
response(data, code, status, headers) |
Full control envelope |
this.error(status, msg, headers?) |
error(status, msg, headers) |
Shortcut error envelope |
this.log(...data) |
debug.log from @axiosleo/cli-tool |
Conditional logging |
All this.success / failed / result / response / error throw, same as the
functional helpers. See koapp-response for envelope details.
Basic usage
const { Controller, Router } = require('@axiosleo/koapp');
class HealthController extends Controller {
async ping(context) {
this.log('ping from', context.request_id);
this.success({ pong: true });
}
async version() {
this.success({ version: require('../package.json').version });
}
}
const health = new HealthController();
const router = new Router('/health');
router.get('/ping', (ctx) => health.ping(ctx));
router.get('/version', () => health.version());
Why use Controller over plain functions?
- Shared state: load DB handles, caches, or config once in the constructor and reuse across methods.
- Inheritance: define a
BaseControllerwith common middlewares or helpers, then extend it per module (theinitscaffolding template atassets/tmpl/services/src/modules/controller.ts.tmpldoes this). - Testability: easier to mock a controller instance than free-floating functions.
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 · 162 lines · 61 tokens per session scan A c8b44503caea
koapp-controller is a skill published in the GitHub repository AxiosLeo/node-koapp (129 stars, last pushed 18d ago), licensed MIT. It adds 61 tokens to every session and 1,249 once invoked, about $0.0003 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…