An interactive process for learning a new project’s structure and connected systems, then creating a project knowledge index. The index records relevant code, database, deployment, and tool information for other agent skills.

Onboarding to an unfamiliar project, scanning its Go files, schemas, migrations, deployments, configuration, and instructions, and generating or refreshing project-index.md and infrastructure notes.

A coding agent cannot reliably use project-specific tools without knowing how the repository and infrastructure are organised. This process creates a shared reference and detects when it is missing or outdated.

onboard — Skill for Claude Code by vmkteam/claude-plugins

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.

Any agent

npx skills add vmkteam/claude-plugins --skill onboard

Clone the repo

git clone --depth 1 https://github.com/vmkteam/claude-plugins

Made for: Claude Code.

Or install vmkteam-developer, the plugin that ships this one along with the rest of its 35 skills.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/vmkteam/claude-plugins/onboard/github.svg)](https://agentmods.dev/skills/vmkteam/claude-plugins/onboard)

Your own site

<a href="https://agentmods.dev/skills/vmkteam/claude-plugins/onboard"><img src="https://agentmods.dev/badge/skills/vmkteam/claude-plugins/onboard/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/vmkteam/claude-plugins/onboard"><img src="https://agentmods.dev/badge/skills/vmkteam/claude-plugins/onboard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 53 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 4,495 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00053	$0.04495
Opus 5.5	$0.00021	$0.01798
Sonnet 5.5	$0.00011	$0.00899
Haiku 4.5	$0.00005	$0.00449

Measured 23d ago against content hash cac19982b0a0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

onboard 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 23d 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.

plugins/developer/skills/onboard/SKILL.md · 381 lines

How it starts

The opening of the file, as written. The whole thing — 381 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Onboard — интерактивный онбординг в проект

Интерактивный процесс изучения проекта. Сканирует структуру, обнаруживает системы, создаёт индексный файл знаний для всех скиллов плагина vmkteam-developer.

Процесс

Шаг 1. Сканирование проекта

Изучи локальную структуру:

go.mod — модуль, зависимости, Go-версия, vmkteam-зависимости
Makefile / Makefile.mk — доступные команды, генераторы
docs/model/*.mfd — MFD-схема, namespace'ы, таблицы
docs/*.pgd / docs/*.pdd — схема БД (определяет: /pgd или /pgmdd)
pkg/ — структура пакетов (db, rpc, vt, domain)
cmd/ — точки входа, бинарники
.gitlab-ci.yml — CI/CD pipeline
deployments/ — Nomad/Docker конфиги
cfg/ — конфигурация (TOML)
migrations/ — SQL миграции
CLAUDE.md / .claude/ — существующие инструкции

Автоопределение vmkteam-инструментов из go.mod:

vmkteam/zenrpc → скилл /zenrpc
vmkteam/mfd-generator (или Makefile mfd-*) → скилл /mfd
vmkteam/colgen (или //go:generate colgen) → скилл /colgen
vmkteam/rpcgen (или Makefile *-client) → скилл /rpcgen
vmkteam/appkit → скилл /appkit
vmkteam/cron → скилл /cron
vmkteam/zenrpc-middleware → скилл /zenrpc
.pgd файлы → скилл /pgd
.pdd файлы → скилл /pgmdd

Определи тип сервиса: API, worker, cron, hybrid.

Шаг 2. Определить стадию и infra-группу

Спроси у пользователя:

На какой стадии проект?

Стадия	Описание	Доступные системы
Идея	Только код, нет деплоя	YouTrack, Git
Dev	Задеплоен на dev/staging	+ Sentry (dev), API dev, возможно Grafana
Production	Задеплоен на prod	+ Sentry (prod), API prod, Grafana, Prometheus, Loki, Nomad

Стадия определяет какие системы спрашивать — не задавай вопросы про Grafana/Prometheus если проект на стадии "Идея".

К какой infra-группе относится проект? (например: acme, platform, storefront)

Проверить наличие shared infra-файла: ~/.claude/memory/infra-{group}.md

Если существует — показать содержимое, спросить актуально ли. Перейти к шагу 3b (только специфика сервиса).
Если не существует — перейти к шагу 3a (полный опрос), создать infra-файл.

Read the full file on GitHub · 381 lines

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.

23d ago Changed · +9 lines cac19982b0a0
1mo ago First seen · 372 lines · 53 tokens per session scan A 49cb509fc4e9

Subscribe to this mod's changes

onboard is a skill published in the GitHub repository vmkteam/claude-plugins (7 stars, last pushed 6d ago), licensed MIT. It adds 53 tokens to every session and 4,495 once invoked, about $0.0002 per session on Opus 5.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-31.

Planning Writing and docs

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens