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/rpcnpx skills add finom/vovk --skill rpcgit 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/rpc)<a href="https://agentmods.dev/skills/finom/vovk/rpc"><img src="https://agentmods.dev/badge/skills/finom/vovk/rpc.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.00354 | $0.06648 |
| Opus 5 | $0.00177 | $0.03324 |
| Sonnet 5 | $0.00071 | $0.01330 |
| Haiku 4.5 | $0.00035 | $0.00665 |
Grade A, and why
rpc 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 — 503 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vovk.ts RPC client
Every controller procedure with HTTP decorator automatically gets typed client counterpart. vovk generate produces these client modules from segment schemas. Import path depends on config:
- Default setup only (composed client + JS template + default
outDir: './node_modules/.vovk-client') →vovk-clientnpm package barrel re-exports emitted.js/.d.ts. Import from'vovk-client'. - Any other config — TS template, segmented client, custom source-tree
outDir—vovk-clientpackage not used. Generated files live in source tree, import through local path alias (e.g.'@/client','@/client/<segment>').
Key identity: client module name = key used in initSegment's controllers map, regardless of import path.
// server
initSegment({ controllers: { UserRPC: UserController } });
// client (default setup shown — composed + JS template)
import { UserRPC } from 'vovk-client';
await UserRPC.getUser({ params: { id: '42' } });
Not UserControllerRPC. Not UserController. Whatever the key is.
Scope
Covers:
vovk generate— when to run, what it produces.- Composed vs segmented clients (
composedClient/segmentedClientconfig). - RPC method call shape.
- Fetcher customization via
createFetcher+outputConfig.imports.fetcher, plus dynamically registeredonSuccess/onErrorsubscribers. - Client-side validation (
vovk-ajvintegration, custom viacreateValidateOnClient). - Error rethrow (
HttpException, status/message/cause,HttpStatus.NULL). - RPC method surface (
.withDefaults,.getURL,.queryKey,.schema,.controllerSchema,.segmentSchema,.fullSchema,.isRPC). - React Query / TanStack Query integration.
openapiandschemapayload imports.- Cancellation — what's supported, what isn't.
Out of scope:
- Segment registration →
segmentskill. - Procedure / handler / validation authoring →
procedureskill. - Streaming clients (async iteration,
progressive()) →jsonlinesskill. - Python / Rust clients →
python/rustskills. @operationmetadata for OpenAPI →openapiskill.
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 · 503 lines · 354 tokens per session scan A c911fe5d3b36
rpc is a skill published in the GitHub repository finom/vovk (52 stars, last pushed 8d ago), licensed MIT. It adds 354 tokens to every session and 6,648 once invoked, about $0.0018 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.