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 dto-slotsgit 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/dto-slots)<a href="https://agentmods.dev/skills/kavo-labs/kavo/dto-slots"><img src="https://agentmods.dev/badge/skills/kavo-labs/kavo/dto-slots/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/kavo-labs/kavo/dto-slots"><img src="https://agentmods.dev/badge/skills/kavo-labs/kavo/dto-slots.svg" alt="Reviewed on agentmods" width="80" 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.00074 | $0.00985 |
| Opus 5 | $0.00037 | $0.00492 |
| Sonnet 5 | $0.00015 | $0.00197 |
| Haiku 4.5 | $0.00007 | $0.00098 |
Grade A, and why
dto-slots 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 10d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DTO slots reference
Every REST verb has an independent, optional data contract. Zero config
means entity-derived defaults; registering a class narrows exactly one slot.
DTOs are shapes for typing, serialization, and Swagger docs only — there
is no validation subsystem attached to them (that's the caller's own
pipe/guard, e.g. Nest's ValidationPipe). Full detail:
docs/internals/architecture/04-dto-system.md. Config-side wiring
(@Kavo(Entity, { dto: {...} })) is in the kavo-decorator skill.
The six slots
| Slot | Verb / context | Default when omitted |
|---|---|---|
create |
POST body |
Entity minus generated + relation fields |
update |
PUT body |
Same default as create |
patch |
PATCH body |
Partial<update> if update registered, else Partial<Entity> |
query |
GET list input |
Generic QueryContext<Entity> |
item |
Any single-resource response | Entity, subject to field selection |
list |
Element type in ListResultDto.items |
Same as item's resolved type |
restoreOne reuses the item slot — there is no seventh slot for it.
Naming convention (CLAUDE.md): request bodies are <Verb><Entity>Dto
(CreateUserDto); query/response shapes are <Entity><Slot>Dto
(UserItemDto, UserListDto).
Each slot resolves independently at bootstrap and is cached on the
resolved config — never re-derived per request. patch → update and
list → item are the only fallback chains; nothing else falls back.
Runtime derivation (when a slot is left unregistered)
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.
- 10d ago First seen · 86 lines · 74 tokens per session scan A d898244c8a12
dto-slots is a skill published in the GitHub repository kavo-labs/kavo (14 stars, last pushed today), licensed MIT. It adds 74 tokens to every session and 985 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-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…
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…
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…