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/multitenantnpx skills add finom/vovk --skill multitenantgit 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/multitenant)<a href="https://agentmods.dev/skills/finom/vovk/multitenant"><img src="https://agentmods.dev/badge/skills/finom/vovk/multitenant.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.00239 | $0.03790 |
| Opus 5 | $0.00120 | $0.01895 |
| Sonnet 5 | $0.00048 | $0.00758 |
| Haiku 4.5 | $0.00024 | $0.00379 |
Grade A, and why
multitenant 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 — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vovk.ts multi-tenant routing
Host multiple tenants from one Next.js app. Each tenant gets own named segment on backend, own frontend page route on frontend, wired together with subdomain-aware proxy calling multitenant() from vovk.
Typical shape:
example.com/→ root tenant (marketing home, or tenant picker).admin.example.com/→ admin tenant — internal backend + UI.customer.example.com/→ customer-facing portal (signup, landing, etc.).<customer>.customer.example.com/→ per-customer instance.pro.<customer>.customer.example.com/→ per-customer pro tier.
Pick any shape; this skill shows wiring for any.
Scope of this skill
Covers:
- Multi-tenant architecture (segments + proxy + frontend pages).
vovk.config.mjschanges (composed → segmented client,segmentNameOverride).proxy.tswiring withmultitenant()helper fromvovk.overridesshape (static, dynamic, nested) and reserved-path guard.- Per-tenant frontend page routes, how they pair with overrides.
- DNS wildcard + local
/etc/hostssetup. - Add-a-tenant checklist.
Out of scope (hand off):
- Creating/configuring individual segment (
initSegment(),segmentName, nested segments, segment priority) →segmentskill. - Writing controllers inside tenant segment →
procedureskill. - Client generation modes (composed vs. segmented,
outDir, templates) →rpcskill.
Architecture
Three layers, one request:
- Proxy (
src/proxy.ts) — intercepts every request, callsmultitenant()with incoming URL, host, youroverridesmap, gets back{ action, destination }. Branches intoNextResponse.rewrite,NextResponse.redirect, or 404. - Named segment per tenant on backend (
src/app/api/admin/[[...vovk]]/route.ts, etc.). Each tenant'sapi/*calls land here after proxy rewrite. - Per-tenant frontend page routes on frontend (
src/app/admin/page.tsx, etc.). Each tenant's non-api requests land here after proxy rewrite.
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 · 263 lines · 239 tokens per session scan A ee704f34a488
multitenant is a skill published in the GitHub repository finom/vovk (52 stars, last pushed 8d ago), licensed MIT. It adds 239 tokens to every session and 3,790 once invoked, about $0.0012 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
ocli-api
Turn any OpenAPI/Swagger API into CLI commands and call them. Search endpoints with BM25, check parameters, execute — no MCP server needed.
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…
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.
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.
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…
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.