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-responsenpx skills add AxiosLeo/node-koapp --skill koapp-responsegit 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.00065 | $0.01574 |
| Opus 5 | $0.00032 | $0.00787 |
| Sonnet 5 | $0.00013 | $0.00315 |
| Haiku 4.5 | $0.00006 | $0.00157 |
Grade A, and why
koapp-response 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 2d 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 — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
@axiosleo/koapp Response Helpers
Source: src/response.js.
@axiosleo/koapp uses throw-based response helpers: you call one of the
helpers and it throws a typed object that the framework's workflow catches
and writes to the wire. This keeps route handlers linear (no need to
return) and lets middlewares/afters run consistently.
Import
const {
success,
failed,
result,
response,
error,
HttpError,
HttpResponse
} = require('@axiosleo/koapp');
Helper reference
| Helper | Signature | Purpose |
|---|---|---|
success(data?, headers?) |
(data: any, headers: Record<string,string>) => never |
200 OK, JSON envelope with code: '200;Success' |
failed(data?, code?, status?, headers?) |
(data: any, code?: string, status?: number, headers?) => never |
Non-2xx with JSON envelope; defaults code: '501;Internal Server Error', status: 501 |
response(data, code?, status?, headers?, format?) |
Full control JSON envelope | Explicit code, status, headers, format (`'json' |
result(data, status?, headers?) |
Raw body pass-through | Bypass the JSON envelope and write data as-is |
error(status, msg, headers?) |
Error with empty payload | Shortcut for response({}, '<status>;<msg>', status, headers) |
All helpers never return - they throw.
JSON envelope
success, failed, response, and error produce the framework's
standard envelope:
{
"request_id": "uuid",
"timestamp": 1714651200000,
"code": "200;Success",
"message": "Success",
"data": { }
}
code follows the "<status>;<message>" convention:
"200;Success""400;Bad Request""404;Not Found""500;Internal Server Error"
Both parts are mirrored into data (so message is still readable when
clients only unpack code). Custom codes are free-form strings.
Raw pass-through with result()
Use result() when you need to emit HTML, plain text, binary, or a pre-built
JSON body without the envelope wrapping:
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.
- 2d ago First seen · 210 lines · 65 tokens per session scan A e94b86ea0eab
koapp-response is a skill published in the GitHub repository AxiosLeo/node-koapp (145 stars, last pushed 19d ago), licensed MIT. It adds 65 tokens to every session and 1,574 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.
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.
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…
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…