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/finom/vovk/decoratorsnpx skills add finom/vovk --skill decoratorsgit clone --depth 1 https://github.com/finom/vovkWrote 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/finom/vovk/decorators)<a href="https://agentmods.dev/skills/finom/vovk/decorators"><img src="https://agentmods.dev/badge/skills/finom/vovk/decorators.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00228 | $0.03871 |
| Opus 5 | $0.00114 | $0.01936 |
| Sonnet 5 | $0.00046 | $0.00774 |
| Haiku 4.5 | $0.00023 | $0.00387 |
Grade A, and why
decorators 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 5d 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 — 329 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vovk.ts decorators
Decorators wrap static methods on controllers. Three kinds:
- HTTP decorators (
@get,@post,@put,@patch,@del) — mark procedure as HTTP route. Seeprocedureskill. - Metadata decorators (
@prefix,@operation) — attach info, no behavior change. - Custom decorators (
createDecorator) — middleware wrapping handler. How auth, logging, feature flags attach.
Two syntaxes: @decorator (needs experimentalDecorators) — default. decorate(...) — function-form fallback, no TS flag; only on request.
Scope
Covers:
@prefixfor route prefixes..auto()for name-derived routes.- HTTP decorator options (
headers,cors). createDecorator— runs before/after handler.- Auth pattern with
req.vovk.meta()state passing. - Stacking order (top-down — outermost runs first).
decorate()alt syntax.- Local (
.fn()) context detection.
Out of scope:
- Writing procedures + validation →
procedureskill. @operationfor OpenAPI docs →openapiskill.@operation.toolfor AI tool derivation →toolsskill.- Next.js middleware (
middleware.ts) — separate, runs earlier in request lifecycle.
@prefix
Class-level route prefix:
import { prefix, get, procedure } from 'vovk';
@prefix('users')
export default class UserController {
@get('{id}')
static getUser = procedure({ /* ... */ }).handle(/* ... */);
}
// → GET /api/users/{id}
Root-level — @prefix('') or omit (same effect):
export default class RootController {
@get()
static ping = procedure().handle(() => ({ ok: true }));
}
// → GET /api
.auto() — name-derived routes
Use method name instead of path:
@put.auto()
static doSomething = procedure().handle(/* ... */);
// → PUT /api/<prefix>/do-something
Method names → kebab-case. Works with every HTTP decorator (@get.auto(), @post.auto(), etc.), same options.
HTTP decorator options
Second arg: response-header + CORS config.
@put('do-something', {
headers: { 'x-hello': 'world' },
cors: true,
})
static doSomething = procedure().handle(/* ... */);
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.
- 5d ago First seen · 329 lines · 228 tokens per session scan A 4727bd26c307
decorators is a skill published in the GitHub repository finom/vovk (52 stars, last pushed 8d ago), licensed MIT. It adds 228 tokens to every session and 3,871 once invoked, about $0.0011 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
client-setup
Create a vanilla tRPC client with createTRPCClient (), configure link chain with httpBatchLink/httpLink, dynamic headers for auth, transformer on links (not client constructor). Infer types with inferRouterInputs and inferRouterOutputs. AbortController signal support. TRPCClientError typing.
adapter-express
Mount tRPC as Express middleware with createExpressMiddleware() from @trpc/server/adapters/express. Access Express req/res in createContext via CreateExpressContextOptions. Mount at a path prefix like app.use('/trpc', ...). Avoid global express.json() conflicting with tRPC body parsing for FormData.
trpc-router
Entry point for all tRPC skills. Decision tree routing by task: initTRPC.create(), t.router(), t.procedure, createTRPCClient, adapters, subscriptions, React Query, Next.js, links, middleware, validators, error handling, caching, FormData.
fast-typescript-check
Keep www-sacred's TypeScript fast to type-check and fast to run. Use when touching the ASCII/canvas animation components (the only real per-frame code here), tightening type-check wall-clock, or auditing a change for runtime or compiler regressions. Scoped to this repo — a React 19 / Next.js 16 component library plus…
port-sacred-terminal-ui-to-typescript-cli
Take a React Window.tsx (or any sacred component) and produce a terminal CLI screen written in TypeScript that uses Simulacrum — the sacred CLI framework in scripts/cli/lib/.
typescript-discriminated-unions
Apply, review, and explain discriminated unions in TypeScript. Use automatically for tasks involving mutually exclusive variants, invalid state prevention, exhaustiveness checking, variant-specific object properties, application state, function arguments, or React props.