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-routernpx skills add AxiosLeo/node-koapp --skill koapp-routergit 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.00087 | $0.01638 |
| Opus 5 | $0.00044 | $0.00819 |
| Sonnet 5 | $0.00017 | $0.00328 |
| Haiku 4.5 | $0.00009 | $0.00164 |
Grade A, and why
koapp-router 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 3d 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 — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
@axiosleo/koapp Router
Source: src/router.js.
Router is the single route-definition primitive for all three application
types (KoaApplication, SocketApplication, WebSocketApplication). A
router can be flat or a tree of sub-routers, and it carries middlewares,
handlers, after-handlers, and validators.
Constructor
const { Router } = require('@axiosleo/koapp');
const router = new Router(prefix, options);
| Arg | Type | Default | Notes |
|---|---|---|---|
prefix |
string |
'' |
Path prefix like /api/v1 or /users/{:id} |
options.method |
string |
'' |
HTTP method. Use 'any' for all methods. Empty string disables the route |
options.handlers |
Function[] |
[] |
Async handler functions async (context) => { ... } |
options.middlewares |
Function[] |
[] |
Run before handlers |
options.afters |
Function[] |
[] |
Run after handlers (even on thrown response) |
options.validators |
object |
{} |
{ params, query, body } - each { rules, messages? } |
Any unknown keys on options are kept on the router instance as-is.
Path params
Use {:name} for path parameters. Legacy :name also works but {:name}
is preferred:
new Router('/users/{:id}/posts/{:postId}', {
method: 'GET',
handlers: [async (context) => {
const { id, postId } = context.params;
}]
});
Wildcards:
/*- matches one segment (captured asparams.<next>if named)/**- matches one segment without capture/***- matches any remaining path, ideal for fallback handlers
HTTP method shortcuts
Each method shortcut creates a nested sub-router:
const root = new Router('/api');
root.get('/users', listUsers);
root.post('/users', createUser, {
body: { rules: { name: 'required|string', email: 'required|email' } }
});
root.put('/users/{:id}', updateUser);
root.patch('/users/{:id}', patchUser);
root.delete('/users/{:id}', deleteUser);
root.any('/health', healthcheck);
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.
- 3d ago First seen · 212 lines · 87 tokens per session scan A b9aab8f21c37
koapp-router is a skill published in the GitHub repository AxiosLeo/node-koapp (145 stars, last pushed 20d ago), licensed MIT. It adds 87 tokens to every session and 1,638 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…