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/vmkteam/claude-plugins/onboardnpx skills add vmkteam/claude-plugins --skill onboardgit clone --depth 1 https://github.com/vmkteam/claude-pluginsWrote 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/vmkteam/claude-plugins/onboard)<a href="https://agentmods.dev/skills/vmkteam/claude-plugins/onboard"><img src="https://agentmods.dev/badge/skills/vmkteam/claude-plugins/onboard.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.00053 | $0.04341 |
| Opus 5 | $0.00026 | $0.02171 |
| Sonnet 5 | $0.00011 | $0.00868 |
| Haiku 4.5 | $0.00005 | $0.00434 |
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 3d 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 — 372 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 pipelinedeployments/— Nomad/Docker конфигиcfg/— конфигурация (TOML)migrations/— SQL миграцииCLAUDE.md/.claude/— существующие инструкции
Автоопределение vmkteam-инструментов из go.mod:
vmkteam/zenrpc→ скилл /zenrpcvmkteam/mfd-generator(или Makefile mfd-*) → скилл /mfdvmkteam/colgen(или//go:generate colgen) → скилл /colgenvmkteam/rpcgen(или Makefile *-client) → скилл /rpcgenvmkteam/appkit→ скилл /appkitvmkteam/cron→ скилл /cronvmkteam/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-файл.
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.
- 3d ago First seen · 372 lines · 53 tokens per session scan A 49cb509fc4e9
onboard is a skill published in the GitHub repository vmkteam/claude-plugins (7 stars, last pushed 4mo ago), licensed MIT. It adds 53 tokens to every session and 4,341 once invoked, about $0.0003 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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.
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…