base

Foundational instructions for Vovk.ts, a TypeScript tool that creates HTTP endpoints and generated clients from backend procedures. They define required project files, schema artifacts, commands, and core API concepts.

In plain words
What is it for?
Use them for Vovk backend work in Next.js projects, including procedures, controllers, segments, RPC clients, schema generation, and the required repository setup.
Why use it?
They give other Vovk instructions a shared set of rules and help keep generated schemas, routes, and client code consistent.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/finom/vovk/base
Any agent
npx skills add finom/vovk --skill base
Clone the repo
git clone --depth 1 https://github.com/finom/vovk

Made for: Claude Code, Codex.

Per session 142 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 617 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00142 $0.00617
Opus 5 $0.00071 $0.00309
Sonnet 5 $0.00028 $0.00123
Haiku 4.5 $0.00014 $0.00062

Measured 2d ago against content hash 1dc4bb398679, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

base scanned grade A with 1 finding 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 2d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- **Plain REST under the hood** — every procedure mounts as normal HTTP endpoint at `/{rootEntry}/{segmentName}/{controllerPrefix}/{methodPath}`. `curl`, `fetch`, any HTTP client works.
skills/base/SKILL.md · 29 lines

What it actually says

Vovk.ts base

Always load. Tiny by design. Detail by topic → owning skill.

Source of truth

Don't WebFetch vovk.dev mid-task. This skill + sibling vovk:* skills = canonical. If something seems missing, name the gap; don't fall back to the live docs site.

Rules

  • .vovk-schema/ — back-end schema artifacts. Commit. Source of truth for codegen on fresh clone.
  • Requirements — Node 22+, Next 15+ (App Router).
  • Templatesjs for vovk-client re-exports; ts for project-source emission. Variants: jsSrc / tsSrc (raw source).
  • _schema_ — dev-only endpoint per segment (when NODE_ENV=development); vovk dev polls these to write .vovk-schema/.
  • vovk dev vs vovk generate — dev = watcher (writes schema artifacts continuously); generate = one-shot (used in prebuild).
  • Plain REST under the hood — every procedure mounts as normal HTTP endpoint at /{rootEntry}/{segmentName}/{controllerPrefix}/{methodPath}. curl, fetch, any HTTP client works.

API surface (brief)

  • InferenceVovkBody, VovkQuery, VovkParams, VovkInput, VovkOutput, VovkIteration, VovkReturnType, VovkYieldType.
  • Coreprocedure, initSegment, controllersToStaticParams, decorate, multitenant, deriveTools, createTool, JSONLinesResponder, progressive, HttpException, HttpStatus, toDownloadResponse, createDecorator.
  • HTTP decorators@get @post @put @patch @del @head @options @prefix @operation.
  • TypesVovkRequest (extends NextRequest), VovkConfig.
Changes

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.

  1. 2d ago First seen · 29 lines · 142 tokens per session scan A 1dc4bb398679

Subscribe to this mod's changes

base is a skill published in the GitHub repository finom/vovk (52 stars, last pushed 5d ago), licensed MIT. It adds 142 tokens to every session and 617 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

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.

EvilFreelancer/openapi-to-cli · 34 tokens

react-performance

Optimize React/Next.js runtime performance — eliminate waterfalls, shrink bundles, cut unnecessary re-renders, and speed up rendering. Use when writing, reviewing, or refactoring components for speed, or chasing slow renders, large bundles, janky interactions, or high TTFB/LCP/INP.

clubpay/ronykit · 64 tokens

ronykit-framework

Orchestrates RonyKit service development using the ronyup MCP server (knowledge resources, prompts, scaffold tools). Use when the user mentions RonyKit, ronyup, EdgeServer, contracts, scaffolding a workspace or feature, implementing API handlers and services, frontend bootstrap, integration tests, or design documents…

clubpay/ronykit · 75 tokens

storybook

Author and maintain Storybook stories with CSF 3.0 best practices — args, decorators, parameters, and config. Use when creating or editing .stories. files, configuring .storybook/, or ensuring every UI component ships with stories.

clubpay/ronykit · 50 tokens

webmcp

Build agent-friendly web apps with the W3C Web Model Context API (WebMCP). Use when exposing frontend features as structured tools for in-browser AI agents, adding document.modelContext tools to React/Next.js apps, designing tool schemas for dashboards or admin UIs, or making existing UI automatable without DOM…

clubpay/ronykit · 69 tokens

composition-patterns

Design reusable React component APIs that scale — compound components, lifted state, generic context, explicit variants. Use when a component is growing boolean props (isThread, isEditing…), when building a component library, or when reviewing component architecture. Includes React 19 API changes.

clubpay/ronykit · 58 tokens