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 skills add kavo-labs/kavo --skill swaggergit clone --depth 1 https://github.com/kavo-labs/kavoWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/kavo-labs/kavo/swagger)<a href="https://agentmods.dev/skills/kavo-labs/kavo/swagger"><img src="https://agentmods.dev/badge/skills/kavo-labs/kavo/swagger.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
What 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.1 | $0.00058 | $0.00825 |
| Opus 5 | $0.00029 | $0.00413 |
| Sonnet 5 | $0.00012 | $0.00165 |
| Haiku 4.5 | $0.00006 | $0.00082 |
Grade A, and why
swagger 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 6d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Swagger / OpenAPI reference
@nestjs/swagger is an optional peer of @kavo/nest — install it and
every generated route documents itself automatically; leave it out and
@Kavo costs nothing extra. No config flag turns this on or off: Kavo
detects the package at runtime (createRequire(...).require("@nestjs/swagger"),
cached, never throws if absent) and documents routes only when it's there.
Full detail: docs/internals/architecture/10-nestjs-integration.md §4.
Install
npm install @nestjs/swagger
That's the only step — no @Kavo config option, no KavoModule option.
Existing @Kavo-decorated controllers pick up documentation the next time
the app boots with @nestjs/swagger present.
Wiring the docs endpoint (main.ts)
This is plain Nest/Swagger, not Kavo-specific — SwaggerModule still needs
to be told to build and serve a document:
import { NestFactory } from "@nestjs/core";
import { DocumentBuilder, SwaggerModule } from "@nestjs/swagger";
import { AppModule } from "./app.module.js";
async function bootstrap(): Promise<void> {
const app = await NestFactory.create(AppModule);
const document = SwaggerModule.createDocument(
app,
new DocumentBuilder().setTitle("My API").setVersion("1.0.0").build(),
);
SwaggerModule.setup("docs", app, document); // → GET /docs
await app.listen(3000);
}
void bootstrap();
What's documented automatically, per generated route
| Piece | Source |
|---|---|
| Operation id | <Entity>_<operationId> (e.g. User_findMany) |
:id path param |
Every operation with an id in its route |
| Query params on list routes | filter/sort/fields/pagination/include shape (doc 05) |
| Request body schema | The entity's registered DTO class for that slot (ApiBody) — see dto-slots |
| Error response schemas | Problem-details shape for 400/404, from the error catalog — see error-handling |
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.
- 6d ago First seen · 79 lines · 58 tokens per session scan A 38ec6648e5d1
swagger is a skill published in the GitHub repository kavo-labs/kavo (12 stars, last pushed today), licensed MIT. It adds 58 tokens to every session and 825 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-09-02.
Other skills, from other repositories
ocli-api
Turn any OpenAPI/Swagger API into CLI commands and call them. Search endpoints with BM25, check parameters, execute — no MCP server needed.
procedure
Vovk.ts procedures — atomic unit of server-side logic in Vovk project. Use whenever user asks to build ANYTHING producing or consuming data on server — page loading data ("users page", "dashboard", "product list"), endpoint, API handler, server action, form submission, controller, validation with Zod / Valibot /…
rpc
Vovk.ts RPC client — how vovk generate turns controllers into type-safe client modules, composed vovk-client vs segmented clients, call shape (apiRoot, params, body, query, meta, init, disableClientValidation, validateOnClient, interpretAs, transform, fetcher), customizing generation via outputConfig.imports.fetcher +…
tools
Building LLM tools with Vovk.ts — deriveTools() (procedures → tools), createTool() (standalone tools, no controller/procedure needed), @operation.tool({ name, title, description, hidden }) decorator, x-tool metadata, ToModelOutput.DEFAULT vs ToModelOutput.MCP formatters, the tools + toolsByName return shape, the meta…
decorators
Vovk.ts decorators — built-in (@prefix, @operation, @get/@post/@put/@patch/@del, .auto()) and custom via createDecorator. Covers authorization / auth decorators, middleware-style wrapping (pre-handler + post-handler logic), req.vovk.meta() for cross-decorator state, stacking order, the decorate() alternative for…
mixins
Vovk.ts OpenAPI mixins — importing third-party OpenAPI 3.x schemas as typed client modules that share the same call signature as native Vovk RPC modules. Use whenever the user asks to "call a third-party API from my Vovk app", "mixin an OpenAPI schema", "import an OpenAPI spec as a client", "wrap an external service…